Remote desktop and console don't work

All Replies

• Sunday, June 21, 2009 1:19 AM

  Moderator

   

   
  

  0

  I am (was) having the exact same problem from all my PC's. RDP and console didn't work but normal network access and backups did. I read this and decided to ping my server by name and got:
  
  C:\Users\mprachar>ping prachar-srvr

  Pinging prachar-srvr.hsd1.ca.comcast.net [208.67.219.132] with 32 bytes of data:

  Reply from 208.67.219.132: bytes=32 time=231ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=190ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=120ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=58ms TTL=51
  
  Tht is NOT the IP of the server or my Comcast IP. SO I pinged it by the real IP:
  
  C:\Users\mprachar>ping 192.168.10.125

  Pinging 192.168.10.125 with 32 bytes of data:
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128

  Ping statistics for 192.168.10.125:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
  
  Ok - that looks right. Let me ping by name again:
  
  C:\Users\mprachar>ping prachar-srvr

  Pinging prachar-srvr [192.168.10.125] with 32 bytes of data:
  Reply from 192.168.10.125: bytes=32 time=1ms TTL=128
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128
  Reply from 192.168.10.125: bytes=32 time=3ms TTL=128
  Reply from 192.168.10.125: bytes=32 time<1ms TTL=128

  Ping statistics for 192.168.10.125:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 3ms, Average = 1ms
  
  Humpf. That's weird. Let me try the console now... and poof it works!? RDP still wouldnt work, so I changed it to access by IP instead of name and then it did.
  
  So, I go to another machine and try the console - still no good. I pinged by name - got wacko 208 IP. Tried the ping "fix but not so lucky this time. ANy ideas?

  
  First, you should start your own thread.  Having said that, it sounds like it might be your router.  Have you tried powering it down, then turning it back on again?  How about flushing the DNS (from command prompt type:  ipconfig /flushdns)?
  • Reply
  • Quote

   
• Sunday, June 21, 2009 2:10 AM

   

   
  

  0
  I am having the exact same issue!
  
  When I ping my server I also get a whacked IP address outside of my domain!!  Where is that coming from because I cant conneect to my console either!
  
  C:\Documents and Settings\John>ping ruckwhs
  
  Pinging ruckwhs.tampabay.rr.com [208.69.32.132] with 32 bytes of data:
  
  Reply from 208.69.32.132: bytes=32 time=75ms TTL=52
  Reply from 208.69.32.132: bytes=32 time=71ms TTL=52
  Reply from 208.69.32.132: bytes=32 time=74ms TTL=52
  Reply from 208.69.32.132: bytes=32 time=76ms TTL=52
  
  Ping statistics for 208.69.32.132:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
      Minimum = 71ms, Maximum = 76ms, Average = 74ms
  
  The actual internal IP address should be 192.168.1.111
  
  I also tried to ping the actual IP address of 192.168.1.111 but it didnt fix mine.
  
  I also flushed the DNS.  and the other wierd thing is it does show the netbios name in the cache, see below.. but still pings wrong and I cannot connect:
  
  C:\Documents and Settings\John>nbtstat -c
  
  Local Area Connection:
  Node IpAddress: [192.168.1.118] Scope Id: []
  
                    NetBIOS Remote Cache Name Table
  
          Name              Type       Host Address    Life [sec]
      ------------------------------------------------------------
      RUCKWHS        <20>  UNIQUE          192.168.1.111       250
  
  • Reply
  • Quote

   
• Sunday, June 21, 2009 2:13 AM

  Moderator

   

   
  

  0
  (split to a separate thread)

  I am (was) having the exact same problem from all my PC's. RDP and console didn't work but normal network access and backups did. I read this and decided to ping my server by name and got:
  
  C:\Users\mprachar>ping prachar-srvr

  Pinging prachar-srvr.hsd1.ca.comcast.net [208.67.219.132] with 32 bytes of data:

  Reply from 208.67.219.132: bytes=32 time=231ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=190ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=120ms TTL=51
  Reply from 208.67.219.132: bytes=32 time=58ms TTL=51
  ...

  The IP address returned tells me that you're using OpenDNS. OpenDNS takes some liberties (i.e. violates some of the relevant RFCs that deal with domain name services) and the result is that their servers will sometimes be returned in a lookup of your server. Please set your router and home computers to use the DNS services of your ISP, and your problem should go away permanently.
  
  

  ---

  I'm not on the WHS team, I just post a lot. :)

  • Proposed As Answer by Ken WarrenMVP, Moderator Sunday, June 21, 2009 2:13 AM
  • Unproposed As Answer by Ken WarrenMVP, Moderator Sunday, June 21, 2009 2:13 AM
  • Proposed As Answer by Ken WarrenMVP, Moderator Sunday, June 21, 2009 2:15 AM
  •  
  • Reply
  • Quote