Server access-pinging
I have a windows server 2003 that when I ping either by using the computer name or ip address, it will ping once under 1ms, then timeout for the rest. This is also an Exchange server and outlook clients will temporarily lose connection and then re-connect. There is one on-board nic. Does it sound like the nic is going bad? I tried changing cables, rebooting, etc.
Last Comment
As you tried changing the IP address and it is working without any issues, proves that the NIC is fine.
The new IP address and old IP are in same network range?
If not then, routing between your system (from where you are pinging) to your server is ok?
The new IP address and old IP are in same network range?
If not then, routing between your system (from where you are pinging) to your server is ok?
Though it isn't entirely clear that this fits the symptoms, I'd still be suspicious that there is a device using the same IP address, though it is set to not respond to pings.
I would suggest connecting the server through a non-managed switch (so there is no IP address in the switch) with just a single PC connected to the switch (along with the server). Try your ping tests again (with both IPs) and see what you get.
I would suggest connecting the server through a non-managed switch (so there is no IP address in the switch) with just a single PC connected to the switch (along with the server). Try your ping tests again (with both IPs) and see what you get.
ASKER
The old and new ip address are in the same range. None of the switches are managed.
I would agree that it sounds like there's a duplicate IP on the network somewhere.
You can help to rule that out by pinging the server from another PC, then running an 'arp -a' and check that the MAC listed for the IP matches the MAC on the server.
If the MAC address from the ARP doesnt match the MAC listed on the server, it confirms that it's a duplicate IP, and you need to find the owner of the MAC address - using a MAC address lookup will at least give you the device manufacturer..
You can help to rule that out by pinging the server from another PC, then running an 'arp -a' and check that the MAC listed for the IP matches the MAC on the server.
If the MAC address from the ARP doesnt match the MAC listed on the server, it confirms that it's a duplicate IP, and you need to find the owner of the MAC address - using a MAC address lookup will at least give you the device manufacturer..
ASKER
I would almost agree that there is an ip address conflict but let me throw one more wrench into the equation. I seem to be able to ping the server by name or ip address from any other server. Now remember also, the switches are not managed but the servers are all on the same switch. I just thought I would mention that in case that is important.
So you can't ping reliably from something connected to another switch though?
On one of the PC's with troubles, try the arp -a command and see if the MAC listed is the actual MAC of the server. make sure the ping is failing when you check..
On one of the PC's with troubles, try the arp -a command and see if the MAC listed is the actual MAC of the server. make sure the ping is failing when you check..
Consider taking one of the non-servers that exhibits this problem and connecting it directly to the switch to which the servers are connected. Retry your ping tests and see what happens. This will help identify whether or not the problem is related to the other switch.
ASKER
I will try that but why would the non-servers ping fine when I change the ip address of the server?
re: why?
Truth is, the scenario defies simple logic. My first presumption is that there is something else going on here that will (likely) make sense once it is identified. I still lean toward another device with the same IP address being present.
Pinning down the symptoms (is it related to which switch you are on? Does it happen when there are no other devices present? etc.) will get closer to identifying the source of the problem.
Truth is, the scenario defies simple logic. My first presumption is that there is something else going on here that will (likely) make sense once it is identified. I still lean toward another device with the same IP address being present.
Pinning down the symptoms (is it related to which switch you are on? Does it happen when there are no other devices present? etc.) will get closer to identifying the source of the problem.
IPsec configured on the server will produce similar results:
Ping xxxxxxxx
Negotiating IP security
Negotiating IP security
Negotiating IP security
Then,
Ping xxxxxxx
Reply
Reply
Reply
Reply
Ping xxxxxxxx
Negotiating IP security
Negotiating IP security
Negotiating IP security
Then,
Ping xxxxxxx
Reply
Reply
Reply
Reply
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Tried my own solution.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER