Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot conect to network

Status
Not open for further replies.

Jorde

Programmer
May 26, 2005
10
US
I hope this post is in the right area.

Working in a computer lab that has a lot of windows 2000 servers running. A while back they were all upgrade to 2000 from Windows NT 4.0 and 1 of the servers could no longer connect to the network.

Everything that is physically outside the box has been check, so there is no problem there, and the switch shows a solid signal from the server.

When I ping 127.0.0.1 and the computer's ip address everyting works fine, but it can not ping the default gateway or anything else. Everything that is listed in ipconfig /all is correct. I have just upgraded it to Windows 2003 to see if the error would be fixed with a freash reformating and installation of a new OS, but the same problem is occuring.

Server is a Gateway 9200 and the NIC is a 3com 905C.

I have checked around the internet and have tried every I could find. I hope someone here can think of something new.
 
Have you tried replacing the NIC?

You can ping 127.0.0.1, but how about the IP that is configured on the server?

When you installed Windows 2003, did you remove the partition or do an upgrade?

I hope you find this post helpful.

Regards,

Mark
 
It seems like HW problem. Don't trust to switch and NIC lights, many times I had bad cables and all lights were OK.
First check if link to switch works physically, connect another computer in place of this server.
If works, try to change NIC.

===
Karlis
ECDL; MCSA
 
Have already replaced the NIC with a new one and tired the new one in 2 different slots. Can ping the IP that I put into the server and the computers name. Also, everything including the cables has been test on another server, so it has to be either hardware or software inside the box itself. Though it is possible I replaced the original NIC with another bad one, it is unlikely. Also, the NIC that was in it was working til the upgrade to 2000. When I upgraded to 2003 I deleted the partition on the harddrive and reformated everything.
 
is there a reservation in dhcp for the ip address it has?
something along those lines...

can you ping it from elsewhere?
and try what karlisi says... see if another pc works in its place.

Aftertaf
________
Regain control of your PC, at
 
Can not ping it from other comps. Another one will work in its place. And eveerything should be fine with the dhcp and the ip adress.

It seem sot me that it almost has to be something that is different in NT than in 2000 and 2003, since the problem started when it was updated from NT to 2000. But any possible hints are appreciated, could easily be something I just overlooked.
 
Deleted it form active directory, still no good.
 
Does this have the firewall enabled? Are you blocking ICMP traffic?

I hope you find this post helpful.

Regards,

Mark
 
As far as I can tell, no firewall si enabled. Installed 2003 and nothign else, so there are no firewalls outside windows, and i cant find one built into 2003. If there is one built into 2003, please tell me how to access it and i will check.
 
Right click the network connection and it is the last tab. Same as with Windows XP SP2.

I hope you find this post helpful.

Regards,

Mark
 
Thanks mark, but no, the firewall is not enabled.
 
This is a server right? Is AD installed or is being used as a worksation or application server, or even just a workstation? you might want try taking it off the network, find a switch and setup a workgroup, submnet or just a seperate network with another computer to see if they will talk, if they do then you know it's software and not hardware.

Are you using DNS? If so, you might want to check the forward lookup zones to make sure there are no weird mappings (I know it's a stretch). You could even try to purge the DNS cache on the computer giving you troubles.. another stretch I know... But worth a try.
 
Thanks for all the great tips ZENYO, but unable to connect it with another comp atm. Right now it is not even actually being used. Because of this problem i have reformatted it so there is nothing installed besides 2003(was seeing if changing from 2000 to 2003 would fix it)

Also, not able to check the forward lookup zones, and have already tried purging the DNS cache on the comp, but it didnt help at all.

If it helps anyone diagnose a problem, after all the stuff i have done it has started showing that it is sending and reciving in the local area connection status, so it seems like it is talking to somthing, but no idea what it could be, still cant ping the default gateway.
 
Some thoughts and questions:

You say you have a lot of W2K server. How many is lots?

What is the IP address you are using on this server, and what is its subnet mask?

Can you temporarily shut down one of the other servers in the lab, and assign its IP address to your server that is not working?

cheers.gif

Help! I've fallen and I can't reach my beer.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top