TCP/IP Problem. Able to send packets, but not receive

[codered10]

Hello all,

I've recently setup an HP Netserver running Windows Server 2003. It has an Intel Pro 10/100 NIC. Initially when I set the box up, I was having problems with not being able to ping or access the box, but I was able to access the internet, etc. from the box. At the time, I tracked it down to the fact that I had remote access/routing installed. I uninstalled Remote Access and everything worked great.

Tonight, I needed to mount the server in a new rack, so I shut it down, made the move, and hooked it back up exactly like it had been before. But, now I am unable to do anything over the network. I am using a static IP, which was not changed from when the system was working.

I've tried repairing the connection. I've disabled and re-enabled the NIC. I've restarted the server several times. Nothing is resolving my issue.

I am unable to ping any other computers from the box, and I cannot ping the box from any other computers. When I open network connections and open the local area connection, it shows that packets are being sent, but the number of packets received is always 0.

Thats about all the details I can think of(though my brain is dead from all the pounding my head against a wall tonight)

Thanks in advance for any suggestions,
codered

Thanks a ton,
codered10

 

[elmurado]

1.Is the NIc sitting properly? What mode is it in? Check under advanced tab for the card in device manager.

2.Have you done ipconfig /all? Open cmd and try.

Try /release and then /renew switches after ipconfig in that order, one at a time.

3.Can you ping loopback address? 127.0.0.1

 

[bobej]

It could be that the network service is not running, check the event log for any clues

 

[codered10]

Okay,

Here are the results of the previous suggestions.

I ran ipconf /all...everything seems to look okay there

ipconfig /release and /renew do not work because I was set to a static IP. I changed the card to DHCP, and received an error that the connection is unable to contact my DHCP server.

The NIC is seated properly, and it shows link lights. Link Speed & Duplex is set to Auto Detect under the NIC properties.

I am able to ping 127.0.0.1. I get 100% response at <1 ms.

I took a look in the event log, and couldn't find anything out of the ordinary in there either.

Any other suggestions?

Thanks,
codered

Thanks a ton,
codered10

 

[elmurado]

What is the DNS setting in network connections?
On ours we tend to have loopback if it is it's own DNS server and the DNS server address if not. Then we have the backup one. Can you ping your gateway--if it's connected to one?

 

[codered10]

DNS setting is to our DNS server 10.51.0.2

I cannot ping our gateway from the machine.

Out of desperation I am currently doing a repair install of Windows Server 2003, but am not overly optimistic.

Thanks for the suggestions

Thanks a ton,
codered10

 

[elmurado]

Can you ping in the opposite direction? ie from 10.51.0.2 to the new server?
What's the physical layer setup between the two? Hubs/switches etc.

 

[codered10]

I cannot ping in the opposite direction either.

The physical layer is fully switched 100M network.

Thanks a ton,
codered10

 

[elmurado]

How about the cat 5? try a new one--you never know....

 

[codered10]

I've already tried four of them. Also tried different ports on the switch.

Thanks a ton,
codered10

 

[elmurado]

Damn! Now you've got me stumped too ...hmmm....

 

[codered10]

Shoot...the way you were asking questions, I was hoping you were going to pull something out of your magical hat for me. It's got me really perplexed right now.

I'll let you know if the repair install solves the issue.

Thanks a ton,
codered10

 

[elmurado]

I'm also assuming you've got the correct subnet mask on there? Seeing as it worked before....
Sorry mate, no magical hats--just going through the layers like I normally do!

 

[codered10]

Yes, subnet is correct.

Thanks a ton,
codered10

 

[elmurado]

One last suggestion--what happens if you set it to DHCP if you can?

 

[LordMarshal]

Curious, do you have VLANS on that switched network of yours? If so, do you control them or do you have a network group that does that? Unless you are in the same physical port you built the server in, it could be a VLAN problem in your switch fabric...

Just something to check...

Hope it helps,
LM

 

[codered10]

Okay,

Repair install of Server 2003 did nothing to help

Switching to DHCP ends up with an Automatic private address...
169.x.x.x

Thanks a ton,
codered10

 

[codered10]

Just noticed under services that WINS is not starting anymore...don't know if it's because of the TCP issues or what.

Anyone suggestions anybody?

Thanks a ton,
codered10

 

[elmurado]

How about giving it a different IP address? Do you have a reserved list of IP's?

 

[codered10]

Okay,

I seem to have had a small breakthrough. I just forced to card to 10M full duplex and i can ping, etc. Forcing back to 100M full results in previous errors.

What would be causing that? Bad network switch? :S



Thanks a ton,
codered10