General discussion

Locked

PC fails to connect to network

By delboy51 ·
I run a 50 PC NT4 network with some of the workstations connecting thru a workgroup. A new Dell 2400 using XP Home was connected a month ago and worked fine until this week. Then it failed to connect with a 'failed to resolve DNS for host' message. I checked cabling and hubs all ok. I can ping 127.0.0.1 but any other IP is unreachable. Ipconfig shows that its using 169.254.181.112 with Subnet 255.255.0.0 and no gateway. /renew gives 'unable to contact your DHCP server' after timeout.
I reinstalled the NIC drivers as well and I think thats about everything I've tried!

Any ideas?
Delboy

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by astewart In reply to PC fails to connect to ne ...

The "169.254...." address is an APIPA assigned address issued by the PC itself indicating that either you have not assigned it a static address on your subnet or it is not recieving a DHCP address if you are using such a server. The default for 2000/XP is to use TCP/IP for network com and not NetBEUI as is the case for NT4. To add the protocol if this is the issue you need to point the add protocol dialogue to Valueadd\MSFT\Net\NetBEUI on the XP CD. For full details look at KB article found on http://support.microsoft.com/default.aspx?scid=kb;en-us;301041

If you are running DHCP I have occaisionally found that giving a PC a static address in the required range, testing connections then reverting back to DHCP will allow the workstation to find the server.

If the NT4 boxes are still running NetBEUI as well as IP it can hide the failure of the DHCP server, try restarting the DHCP server.

Collapse -

by delboy51 In reply to

Poster rated this answer.

Collapse -

by delboy51 In reply to PC fails to connect to ne ...

Thanks for the response
I am using TCP/IP for networking.
Tried setting a static IP but still responds the same. Returned to DHCP, again no change. Your last point, if DHCP at the server had failed wouldn't all workstations have the same problem?

Delboy

Collapse -

by astewart In reply to PC fails to connect to ne ...

You can specify the duration of a lease in the DHCP server configuration, are you using the W2k server application. You can see what leases are currently active, see if any have been issued recently also do "/renew" on a working PC and see if the lease issue is updated.

I am a little concerned about the status when a static address is in effect. Your DHCP server should have a static address as well so when the XP PC has one in the same range you should be able to ping each other, can you?

Are the lights on at both ends of the Cat5 cable, you can have a light on at the PC and not the other end with a faulty cable.

Collapse -

by delboy51 In reply to

Poster rated this answer.

Collapse -

by ustek In reply to PC fails to connect to ne ...

Because DHCP is not available so by default
Windows assigns M$'s ip: 169.254.xxx.xxx.
Set static ip, check cabling, ping your own ip, ping default geteway ip etc.
RTFM

Collapse -

by delboy51 In reply to

Poster rated this answer.

Collapse -

by statykserver In reply to PC fails to connect to ne ...

Check the activity lights on the back of the computer where the network card is. When you gave it a static ip address were other computers able to ping the one you gave a static ip? Also do you know which port on the hub the system is connected to? Try unplugging the system and see if there is any change on link lights on the hub to see if there is even a connection. Another thing you can try is to uninstall tcpip then shutdown the computer. Restart and reinstall tcpip allowing dhcp again.

Collapse -

by delboy51 In reply to

Poster rated this answer.

Collapse -

by willcomp In reply to PC fails to connect to ne ...

Download and run winsockfix.exe available at link below.

http://www.tacktech.com/display.cfm?ttid=257

This handy little program has been a lifesaver when dealing with XP systems since you can't uninstall and reinstall DUN to restore winsock.

Dalton

Back to Windows Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums