My Server was running fine yesterday; but, today I am unable to access it. Here are the errors:
Remote Desktop Connection --------------------------- Remote Desktop Connection --------------------------- This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. --------------------------- OK Help ---------------------------
Windows Home Server Console
--------------------------- Windows Home Server Console --------------------------- This computer cannot connect to your home server. Check your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes. --------------------------- OK ---------------------------
--------------------------- NET WORK RESULTS FOR SERVER
babygirl Computer Name: BABYGIRL Status: Online IP Address: 192.168.1.102 Subnet Mask: 255.255.255.0 MAC Address: LEFT BLANK Operating System: Microsoft Windows Server 2003 (Server) Processor: Not Available Memory (RAM): Not Available Shared Folders: 0
Can PING with no problem reported
Microsoft Windows [Version 6.1.7100] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 192.168.1.102
Pinging 192.168.1.102 with 32 bytes of data: Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.1.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Windows\system32>ping babygirl
Pinging babygirl [192.168.1.102] with 32 bytes of data: Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=6ms TTL=128
Ping statistics for 192.168.1.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 6ms, Average = 1ms
C:\Windows\system32>
All computers are hard wired except one machine, Which I did this Ping from. Network Magic shows all connected. Servers boots with no problem. Password has been VERIFIED?
My Server was running fine yesterday; but, today I am unable to access it. Here are the errors:
Remote Desktop Connection --------------------------- Remote Desktop Connection --------------------------- This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. --------------------------- OK Help ---------------------------
Windows Home Server Console
--------------------------- Windows Home Server Console --------------------------- This computer cannot connect to your home server. Check your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes. --------------------------- OK ---------------------------
--------------------------- NET WORK RESULTS FOR SERVER
babygirl Computer Name: BABYGIRL Status: Online IP Address: 192.168.1.102 Subnet Mask: 255.255.255.0 MAC Address: LEFT BLANK Operating System: Microsoft Windows Server 2003 (Server) Processor: Not Available Memory (RAM): Not Available Shared Folders: 0
Can PING with no problem reported
Microsoft Windows [Version 6.1.7100] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 192.168.1.102
Pinging 192.168.1.102 with 32 bytes of data: Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.1.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Windows\system32>ping babygirl
Pinging babygirl [192.168.1.102] with 32 bytes of data: Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time<1ms TTL=128 Reply from 192.168.1.102: bytes=32 time=6ms TTL=128
Ping statistics for 192.168.1.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 6ms, Average = 1ms
C:\Windows\system32>
All computers are hard wired except one machine, Which I did this Ping from. Network Magic shows all connected. Servers boots with no problem. Password has been VERIFIED?
Don't know what to try next. Need some HELP!!
THANKS IN ADVANCE.
CarolinGuy
Can you connect to the server at all? Does the Console work? Can you access the server's shares? Can you backup a client? Can you open a RDC? It seems really bizarre that you can successfully ping both by name and by IP address, but nothing else works.
No matter what I try; it gives me an error nad says to check my internet connections. Really weird.
I was able to get on one time with RDP and it HUNG on the waring page.
CarolinaGuy
Have you tried rebooting your server (which might require a hard shutdown of your server if you can't connect to it)? What color is your WHS icon in your system tray? Is this a pre-built server (i.e. HP or Acer) or did you build it yourself? How long has it been up and running before this started?
Proposed as answer bykariya21ModeratorTuesday, September 15, 2009 4:16 AM
Thanks for your help. I rebooted the system today and everything booted fine as before. On start-up of the Desktop it gave me an error that somethings was amiss on the last start with a CHOICE of RETRY & SKIP.
I chose RETRY and the system booted up. Have tried several reboots with no problem.
I built the system myself and put it on line on 1 Maty 2009.
