IP Issues

[treyhunsucker]

So basically my system is a nice IBM server, with great specs, but a couple days ago I restarted it and now neither one of the onboard nic's work.

1 of them originally had a static ip, and the other one was disabled. I have since took the static off the 1st adapter and after booting up it does pull a dhcp address. However I can't ping anything in the network and of course no internet. Once I release the ip and try to renew, it fails.

This makes me think that there is something running to cause this. I've checked event viewer and ran spyware/virus utilities including sfc /scannow and everything looks good.

I also installed a pci network card that did the same thing, along with a usb wireless card. I've dug and dug and dug but haven't found anything, what am I missing here?

There are hours and hours of work on this server and would really like to avoid having to reinstall the os. Any ideas?

 

[lowrad]

Hello.

So everything worked fine before you rebooted?
A server is supposed to have a static IP address.
Look in DNS and see if the Server has a registered IP.

Can you set a static IP and show me the ipconfig /all printout?

To use a DHCP address on a server should be considered a crime by the way, so don't every use it for anything else than clients =)

 

[treyhunsucker]

Using DHCP for a server shouldn't be considered a crime, anyways thats not related to this problem.

I moved this server to a different office (closer to my house) and there is a simple linksys router there, and no other servers.

I tried dhcp and static (different subnet there) and still had the same problem.

I can only type out the ipconfig because obviously it has no internet access, but I assure you that all my information is correct.

 

[juniper911]

Trey

When you changed the NIC to be DHCP, you said that it was getting an address. Was it an address issued by your DHCP server or one beginning with 169.254?

If its issued by the DHCP server then you cannot have anything wrong with your NIC, check the details that the DHCP server is sending.

If the address starts with 169.254 then the problem is that it cant communicate with the dhcp server or there is a problem with the NIC.

Just do basic connectivity tests like ping a machine on the same subnet and then on another in a another subnet.

Also how do you get to the internet? Do you use a proxy server in between?

 

[treyhunsucker]

The unit was pulling the correct ip, in the correct subnet

192.168.1.150
255.255.255.0
192.168.1.1
Linksys router, directly connected to the internet

What fixed the issue is uninstalling and then reinstalling tcp using the process found here:

http://support.microsoft.com/kb/325356

Posting on forums are frustrating because I always try the basic stuff, I come here when something just doesn't seem right....