• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 316
  • Last Modified:

I can't ping a server on a subnet, that I previously have connected via remotwe desktop.

W2K3 Single Domain, GC,DC. Exchange all resident on one box. I have a server (W2K3 also) at a remote location that I previously connected to via remote desktop. Suddenly can't ping nor attach to server. Users at this site can still access network resources here. My isp has checked router and router to server is o.k. Can some one offer a plan for diagnosis?
0
arnevee
Asked:
arnevee
  • 5
  • 3
  • 2
2 Solutions
 
rsivanandanCommented:
How about posting the 'tracert <ip>' output here ? do it twice. One to the server which is not working and one to another machine there which is working.

Cheers,
Rajesh
0
 
Walter PadrónCommented:
Use portqry to verify if port are filtered

"New features and functionality in PortQry version 2.0"
http://support.microsoft.com/kb/832919

portqry -n yourserver -e 3389
0
 
arneveeAuthor Commented:
Am attempting both suggestions, thanks. Will inform.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
arneveeAuthor Commented:
I did a tracert by host name, any other computer on this subnet... I can get to in 3 hops.
This one gives me two hops an request times out(30 hops).
Am I missing something basic?





0
 
Walter PadrónCommented:
No, is just the server filtering ping probes. Check if the firewall service is started.
0
 
arneveeAuthor Commented:
Do you mean at the remote server?
0
 
rsivanandanCommented:
So are there 2 routers in between these networks ? Paste both the output here.

Cheers,
Rajesh
0
 
arneveeAuthor Commented:
I do not have ready access to remote location. I have  also been advised to  check rdp-tcp listening.
Will advise. Thanks All.
0
 
arneveeAuthor Commented:
BTW: Could figure out  PortQry Tool...
0
 
Walter PadrónCommented:
You can also test server port 3389 from a computer at remote site

- if Filtered then the server has a firewall up or the service is down.
- if NOT Filtered the router is discarding the packets.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now