Discussion Locked

Networking / Internet Issues on XP

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am trying to resolve this today:
Got a home network on a router. 3 machines already use the net and (kind of) share files. I got PC4, freshly loaded XP Pro, but it can not see the network or use the Net. The light on the router is on, but the router software not see it.
IP detection set for automatic. I loaded this up with 98SE and XP before this week (doing software installation tests) and they were able to use the network before. This next time around it does not.
How can I get this XP machine to use the network?
No file sharing works. I do IPCONFIG and it gives me no info.
Thank you.

15 replies

by sgt_shultz

sounds like you got everything right except maybe you are not getting valid ip address. i think you are barking up correct tree with ipconfig and that it gives you no info is maybe big clue. do it on a working pc, one that can use the internet. see any difference from bad pc. think maybe: Yes! then try ipconfig /renew at command prompt on bad pc and if that doesn't fix it tell us any error you get (ie what happens when you use ipconfig /renew). you could also try your hand at manually setting ip address, subnet mask and gateway if no joy with ipconfig. look at ip settings (use ipconfig) on working pc and make same on bad pc except ip address must unique as you know so make list of addresses used on your little network and pick next number. if this gets you going then you know dhcp client on bad pc not able to get good number for some reason (usually minor) and you can tshoot from there. if you had said that ipconfig looked normal i would say make sure network connection is not xp firewalled. you are close. very close.

by borginva

On the working machines, I get, for example:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

On the non-working one, I get :

Ethernet adapter Local Area Connection:

Nothing more from this point. No idea what to do.

by borginva

Nothing there was helpful. I get no info on any IP. I go to STATUS and SUPPORT on my local LAN info and it shows nothing for the TCP/IP settings. Whether I manually put them in there or not in the properties of the TCPIP section in the NETWORKING OPTIONS.
Not even its own shared files show up in the domain (HOME).

by borginva

UPDATED INFO

When trying to REAPIR the current LAN connection, it says:

Failed to query TCP/IP settings of the connection.

Still, the router light is on for this machine.

by borginva

PLEASE, EVERYONE POST BACK WITH JUST A COMMENT, so that when the correct asnwer is found, all that helped with valid and useful info will get credited.
Sorry for closing out each response (long day). So if you already answered, please post back. Hopefully if this is resolved tonight!!!, I can award points to all who helped get me back up and running.
Thanks

by joseph moore

Since this is an XP box, you can run NETSH which comes with it. NETSH is a Resource Kit that Microsoft wisely added to XP installs by default.
It runs similar in structure to working on a Cisco router (use the ? as help)
So, open a Command Prompt, and type NETSH.
That will bring you to a NETSH> prompt
Then run INTERFACE DUMP to get a whole list of the interface info. This will show us exactly what interfaces are on this machine, and what they are set to.

It also might be helpful if you run a DUMP command from the NETSH> prompt also, but that will give all IP information for your machine. It is very long, and might be difficult to post here at TR.

Another useful NETSH command, from the NETSH> prompt is INTERFACE IP RESET which would reset all IP configs for your network cards.

NETSH is a good program to use to look at the IP working in XP. Take a look at it.

by curacao_dejavu

update the driver for the nic or try use a known workig nic (preferable that is already certified by MS thus on the hcl list.

by curacao_dejavu

try also to remove the tcp/ip protoc reboot, and add it back again.
Did you check in eventviewer to see if there are any conflicts ?

Leopold

by borginva

Yip! I did all this many times. Removed the hardware drivers and back again, no good. I ended up reloading this box (yet again) and this time it all worked.

This discussion is closed to new replies.