[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 341
  • Last Modified:

Windows Server 2003 IP ping times out

If I ping my static IP address that my server is behind it times out i.e. the server doesn't exist.

If either of the pings time out, fail, or do not return the correct values, then either the DNS lookup is not working properly or there is some other networking or routing issue that you will need to resolve.

I found this error description online at http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

my IP is 204.13.8.9 the server is behind a network router and is a file sharing server with Windows Server 2003 R2 installed.

Can someone help me get this to work?
0
wilsoada
Asked:
wilsoada
1 Solution
 
duffman76Commented:
Do you have a hardware/software firewall in place that is blocking ping requests?  If you are trying to ping by the ip address and not the name then DNS should not be an issue.  Can you ping anything that is behind the router or is it just this server that times out?
0
 
MrLonandBCommented:
Do a tracert: tracert xxx.xxx.xxx.xxx and see where the connection stops.
0
 
LauraEHunterMVPCommented:
Is the Windows Firewall enabled?  R2 will have the WF enabled by default, which will block ping requests by default.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
wilsoadaAuthor Commented:
If i try to run the WF the OS throws an error: Windows FIrewall can not run because another service is running that might use the network address translation component Ipnat.sys so I can not open the WF to see if it is blocking things.
0
 
duffman76Commented:
Go and stop the RRAS service if you are not using it.  That is usally the service that holds on to ipnat.sys
0
 
duffman76Commented:
You can also run the command net stop ipnat.sys which will stop NAT and allow you to configure the firewall.  You can start it again with net start ipnat.sys after you perform the configuration.  
0
 
wilsoadaAuthor Commented:
system error 1060 has occurred the specified service does not exist as an installed service if i do the net stop
0
 
wilsoadaAuthor Commented:
Also get te same error if I do net start. I am executing these commands from the command prompt. Also, I could not find in the windows task manager any service running by the name of RRAS and I don't know what that is.
0
 
wilsoadaAuthor Commented:
RRAS = Routing & Remote Access under Administrative Tools, note that this will erase any set configuration of the RRAS and you will need to re-run the setup for it after you make your changes to the WF if you need the RRAS running.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now