Answered by:
cannot connect to server

Question
-
i have read through some of the threads here and did not find my answer, if there is one sorry about this post. My trial of WHS expired and so i purchased the new software and installed it. Ever since i have had issues where the server is on but will not show up in the network or even if i try and remote desktop it using logmein it claims the computer is offline. The only way i can get it to work again it to power completely down and restart. The server software recognizes the NIC and the active link light does blink so it is communicating but i can't connect to it. THanks for your time.Tuesday, February 10, 2009 4:21 AM
Answers
-
LckyBy517 said:
Now what?back to answering the questions in my first posting would be a possible start (like the request for the client and server output of ipconfig /all).
Also, while locally logged on on the server desktop click Start/Control Panel and select System.
On the Remote Tab uncheck the checkbox for Remote Desktop, click Apply and check it again.
In Windows Firewall check, if the Remote Desktop exception is still enabled.
Best greetings from Germany
Olaf- Proposed as answer by Olaf EngelkeModerator Monday, February 23, 2009 9:22 PM
- Marked as answer by kariya21Moderator Tuesday, February 24, 2009 1:23 AM
Sunday, February 22, 2009 9:18 PMModerator -
Alright guys i got it working, turns out that the remote desktop was disabled for some reason, i enabled it and it works now. Thanks for the help.
- Marked as answer by kariya21Moderator Tuesday, February 24, 2009 1:23 AM
Monday, February 23, 2009 7:06 PM
All replies
-
Hi,
some things to check:
Can you ping the server by name and IP address from the client and from a local session to the server in this situation?
What is the output of
ipconfig /all
issued in a command line on a client and the server?
The network drivers on the server are up to date (and also the firmware of the router)?
On the server it may help, to open Device Manager, double click the network adapter, select the Power Management tab and uncheck the option "Allow the computer to turn off this device to save power."
Does your server have more than one network adapter installed? If yes, disable the second NIC in device manager. In Control Panel/Network Connections on the server in menu Advanced/Advanced Settings check, that the LAN connection is on top of the list.
Do you have any other protocol installed on the client or server besides TCP/IP? (i.e. IPX) If yes, remove it.
Best greetings from Germany
Olaf- Proposed as answer by Olaf EngelkeModerator Wednesday, February 11, 2009 1:13 PM
- Marked as answer by kariya21Moderator Thursday, February 12, 2009 2:36 AM
- Unmarked as answer by moose517 Saturday, February 14, 2009 3:34 AM
Tuesday, February 10, 2009 8:53 AMModerator -
duh i can't believe i forgot to disable the power saving mode on the NIC, i did that last time and just forgot to set it now. Personally i think that should be disabled by default since the server should probably have a active link at all times. Thanks for the help though olaf engelkeWednesday, February 11, 2009 5:25 AM
-
well so i thought it was solved, i got home from work and went to transfer over a folder and its showing the server is not connected again. Maybe i just need to do a complete new installation of it and just pull all the data off and put on my computer and just reformat the entire thing.Saturday, February 14, 2009 3:34 AM
-
Hi,
I don't think, that a new installation will bring you too much. The reason for loosing connection must be somewhere else, and a fresh installation would not fix it.
Please check the event log of your server, if you can find any error messages here.
Try another network port and cable, also check, if you have the most up to date drivers for the network card installed (not at the site of the mainboard maker, but on the site of the maker of the network chip).
What for a network adapter is it? Sometimes people had to recognize, that the onboard cards did not work reliable and an additional NIC with Windows Server 2003 drivers would perform much better.
Does your server go to standby or hibernate at any point?
Also go back to the other questions in my first answer.
Best greetings from Germany
OlafSaturday, February 14, 2009 8:07 AMModerator -
This is moose517, i think i used my other account to log in LOL. alright, well i know you said that a fresh installation wouldn't fix it, well so far it has, for the most part it did. The server has not gone offline for any reason, i can open the shared folder and access everything still, its been 3 days so it might be fixed but it might not of as well. But a new problem has risen, when i try and open the console it says that "This computer cannot connect to your home server. Check your network connection and make sure your home server is powered on. If your homer server has recently restarted, try again in a few minutes." this always pops up from either of the computers that i have reinstalled the connector software on. I tried resetting the console as well and that hasn't done any good. And the last time the server was rebooted was over 3 days ago as well. I appreciate your help olaf, maybe this one will be easy enough to fix.Friday, February 20, 2009 5:54 AM
-
Hi,
that might not be as simple as you assume, since I have more often seen the contradictionary result - connector not connecting, but console access still works.
Did the server change it's IP address during the reinstall? And did you alter the hosts files on the clients in the past by adding the reference IP address - server manually to solve name resolution problems? In this case the entry may still point to the old IP address and be the cause for your described issues.
What happens, if you run discovery.exe from C:\Program Files\Windows Home Server on the clients?
Best greetings from Germany
OlafFriday, February 20, 2009 8:09 AMModerator -
if i run discovery.exe it goes throgh and finds the server just fine but when i try and open the console again it doesn't work. I can also ping it just fine as well. I have never altered the host files either cause i don't know where that would be done LOL.Friday, February 20, 2009 2:34 PM
-
Hi,
can you connect to your server with the Remote Desktop client? If this also fails, does your server have a NVidia video card and got drivers for this installed or updated just before the issue happened the first time?
In this case the information in this thread can help eventually.
Best greetings from Germany
OlafFriday, February 20, 2009 6:58 PMModerator -
which remote desktop client should i be using to try and access it? I do have a nvidia card installed but i don't have the drivers installed for it, however back before i started having issues i did have the drivers installed and was fine, after i did the initial reformat for the new key i didn't bother installing the drivers. I tried installing the nvidia drivers just to see if that would work and it hasn't yet, but it did just restart so i'll check a little later and report back.Sunday, February 22, 2009 4:35 AM
-
Hi,
your Windows (XP or Vista) has a Remote Desktop Client in Start/All Programs/Accessories (or a similar path) - this is fully enough to test this.
Best greetings from Germany
OlafSunday, February 22, 2009 5:56 AMModerator -
alright, i just tried using windows remote and it didn't work either.Sunday, February 22, 2009 10:09 AM
-
Hi,
did you try the registry hack mentioned in the other thread (followed by a server reboot)?
In the Event Viewer on the server, are there informational entries pointing to the file rdpdd.dll?
Did you try remote desktop via name or also using the IP address? (User name Administrator, password the console password)
Best greetings from Germany
OlafSunday, February 22, 2009 10:59 AMModerator -
Alright, tried the registry hack and that didnt work, i uninstalled the nvidia drivers and redid the registry hack and still no go. I checked the event viewer and seen nothing as far as rdpdd.dll I also did try remote desktop with both the name and IP and that didn't work as well. Now what LOL?Sunday, February 22, 2009 8:38 PM
-
LckyBy517 said:
Now what?back to answering the questions in my first posting would be a possible start (like the request for the client and server output of ipconfig /all).
Also, while locally logged on on the server desktop click Start/Control Panel and select System.
On the Remote Tab uncheck the checkbox for Remote Desktop, click Apply and check it again.
In Windows Firewall check, if the Remote Desktop exception is still enabled.
Best greetings from Germany
Olaf- Proposed as answer by Olaf EngelkeModerator Monday, February 23, 2009 9:22 PM
- Marked as answer by kariya21Moderator Tuesday, February 24, 2009 1:23 AM
Sunday, February 22, 2009 9:18 PMModerator -
LckyBy517 said:
Alright, tried the registry hack and that didnt work, i uninstalled the nvidia drivers and redid the registry hack and still no go. I checked the event viewer and seen nothing as far as rdpdd.dll I also did try remote desktop with both the name and IP and that didn't work as well. Now what LOL?
Are you able to logon if you connect a keyboard, mouse, and monitor to your server? If so, can you look at the settings for Windows Firewall and see what they are?Sunday, February 22, 2009 9:22 PMModerator -
Alright guys i got it working, turns out that the remote desktop was disabled for some reason, i enabled it and it works now. Thanks for the help.
- Marked as answer by kariya21Moderator Tuesday, February 24, 2009 1:23 AM
Monday, February 23, 2009 7:06 PM