Router not recognised

[~Root~]

i was just browsing through this. but you i know i had a similiar problem on a network install i did 6 months ago. the Nic was enabled but the drivers would set it to static ip addresses and as soon as you would switch it to dynamic it wouldnt finish loading TCP/ip configurations.

i had to uninstall/re-install the nic. took care of the problem.

P.s. - what is you Default Gateway ip(Dlink Routers usually set by default at 192.168.0.1) some times, if your getting a router from a ISP they set up the DHCP server on ther router to non-standard ip's. so you cant just open the manual and go mess around with it.

if i were you i would,

1. Check all physical Connections.

2. Check ip Status(either by Start > Control Panel > Network Connections| (your ethernet adapter) > Right click on the adapter > Status > support| and check to see if you have a IP in the 192.168.0.2 to 192.168.255.254 range) or by opening Start > Run > typing in "CMD"(without Qoutes). when MSdos opens infront of you typing "ipconfig /all", Look for your Ethernet Adapter again, and check the ip like above.

3. open Internet Explorer(or Mozilla, Solaris, Kbrowser, Firefox, Etc.. Choose your flavor lol) and type in http://(default gateway ip here)/ (Example: http://192.168.0.1/)

and you should be prompted for the username and password. enter the defaults provided or what ever the password is currently set to (pass on your model by default is "default")

4. go to the Status page, and check your "wan ip" contact your ISP to verify these settings.

_____________________________________________________________

If you have any more problems or need more help feel free to pm me - im just trying to provide you a little help, i know how annoying it can be.

Edited by -pops- to remove an email address that could have been picked up by address harvesters - as per your other post, ~Root~

[JesseJ1935]

Thanks for your reply root, it is something else to try.

I'm afraid that illness has reared its ugly head which is preventing me from doing anything at present but as soon as I am able I will report back.

Thanks again.

[snowdins]

the problem is with the via rhine II ethernet adapter.. its not the router, or the cables, or windows xp, or the drivers.

the nic is a piece of junk and i can't understand how it is still being manufactured. just got a motherboard with this thing in it and get limited or no connectivity all the time.

call the manufacturer of your motherboard and tell them you want a rma. infact tell them you dont want the motherboard and then go get a new one that has nothing to do with VIA.

VIA manufactures parts at a low cost. you pay low you get low reliability.

[leefan]

im not sure if i should be cutting in here or not, but i just wanted to say that evidently her network assigns dynamic ips. normally, for a router, the router should come ready to be used without much setup. all routers come with a set default gateway, so if you know that much, you could probably access your router's configuration files via IE, by typing in the default gateway into the address bar.

when a router fails to assign ips, there are two possible ways to go about it: resetting the router, or manually assigning an ip. both of these you mentioned:

PPPoEWin Miniport

VIA Rhine II Fast Ethernet Adaptor

are network cards, judging by their names. what i suggest is going to my network places and i believe, you should be using local area connection. double click it, and one of the above mentioned hardware should be listed under "connect using." from here, in the list, click internet protocol(IP/TCP) and choose to use ip provided. in there, input the default gateway and subnet mask (which normally looks something like 255.255.255.0) and chosen ip address, which, assumming your ip was 123.456.7.8, you would most likely enter something like 123.456.7.800, 123.456.7.801, and so forth.

of course, im not an expert in networking, and in the case that im completely off, i apologize for the inconvenience, although i do have experience from managing my home network and having a cousin who did a few years networking for blizzard.

[JesseJ1935]

Thank you leefan, I certainly don't class it as cutting in, I'm pleased you went to the trouble to do so, every scrap of information could help, and it micht well be your contribution that does the trick.

For reasons I don't need to go into here, I haven't felt up to dong much at all just lately, but I will be during the next couple of days and will follow up all the suggestions previously made.

Will post back with the results.