Solved

Sudden ping destination host unreachable on 2003 server

Posted on 2008-10-02
4
2,066 Views
Last Modified: 2008-10-07
We have a 2003 sp2 server set up as  a print server ("w3").  It was working fine this morning with the exception of one printer.  The server was rebooted (it did show that a MS patch was applied and update required).  After reboot we cannot ping in our out to server w3.

On further investigation, the server has lost the ability to connect:
- 2 network cards on w3 server, both behave the same
- Setting network connection to dhcp will obtain an ip address from dhcp server
- Manually changing the IP to static address will change the ip address
- If you ping the w3 server from another server by the dns name, the IP address associated reflects the changed IP address.  However, ping returns request time out.  Pinging by IP address also give request time out.
- doing a ping to self on w3 server returns correctly.  
- can do looptest on w3 server.
- doing a ping from w3 server to another server returns "Destination host uncreachable" as opposed to request timeout.

The patch that was applied was kb948496.  We uninstalled it.  

Any suggestions as to what to try would be greatly appreciated.  Everyone is needing to print...
0
Comment
Question by:okcuser
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 3

Expert Comment

by:BigCasino
ID: 22626788
Did the update enable any kind of firewall functionality?
0
 
LVL 18

Expert Comment

by:sk_raja_raja
ID: 22626971
Also try to ping from that server to someother machine...most probably firewall should be turned on...you can turn it off and all will be good...typical known MS issue
0
 

Accepted Solution

by:
okcuser earned 0 total points
ID: 22627004
I think I found the solution -
http://www.experts-exchange.com/Networking/Windows_Networking/Internet_Protocols/Q_23571660.html?sfQueryTermInfo=1+870910

I looked and we do have the IPSec blocking error

I'm trying to follow the instructions at
http://support.microsoft.com/default.aspx?scid=kb;en-us;870910 
to repair the policy,
but I don't have the registry key below microsoft.  
0
 

Author Comment

by:okcuser
ID: 22627222
That fixed it.  Thanks anyway!
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question