(This belongs in the "Windows Home Server Hardware and Installation" forum. But theSelect a Forum Category /Select a Forum listboxes do not offer that as an option, so I picked the closest I could find.) I have a (headless) HP MediaSmart Server. I cannot connect to the server across the ethernet connection at all. Up until recently, it had been working fine for about a year. Upon a cold boot, for the first 3 or 4 minutes, I can ping the server from a different machine on the network (with response times of 1-4 milliseconds, as you would expect). After four minutes, if it responds to the ping at all, the response come in the 5 to 9 SECOND range, which is ridiculous. Ping seems to work until the OS is fully booted. I cannot connected via the Console (icon always grey), nor through RDP. The server appears in the network neighborhood, but I can't reach the shares. It's possible that it auto-downloaded a flaky update to the NIC driver but the important point is I have no idea what is going on, since it has no local monitor or keyboard. Everything else on the network in fine. (Other machines, hard-wired & Wifi, can commicate with each other & the internet). The health led is usually blue (on some reboots, it's red, but I assume that's a different problem which I'll deal with once I can log on) Any ideas on how to diagnose/solve this problem? Truth, James (http://www.honestillusion.com)

hi james, There are different components included in troubleshooting the issuewe would like to know what happens when you are trying to ping from a local subnet ?which mean try doing RDP from local subnet and check ifyou still experience the issue.second option is to update the NIC driver , it might be older version which you are using whch might be responsible .are there any other issues ? on this server such as file sharing etc.. or only just ping.You can change the switch port and check if the issue occurs ? for thisyou need to have the control of the server , if not troubleshooting would be difficult. if windows home server uses Remote Desktop 6.0 then it leverages a new feature called auto-tuning for the TCP/IP receive window that could be causing the trouble.try running the below commands Type: netsh interface tcp set global autotuninglevel=disabledif you want to re-enable it Type: netsh interface tcp set global autotuninglevel=normalsainath !analyze

Hi James, Please perform Sainath's suggestions. I the issue persists, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding. For your convenience, I have list the related link as followed. Windows Home Server Hardware and Installation http://social.microsoft.com/Forums/en-US/whshardware/threads Note: Windows Home Server Hardware and Installation is available. Best regards, Vincent Hu

thank you vincent , i thought home server forum is not there.sainath !analyze

Hi Sainath, So I got the wrong forum for Windows Home Server? What's the right place should be? I can only find the above one. Best regards, Vincent Hu

hi vincent, actually i thanked you for the link, because i was not able to find the forum :)sainath !analyze

Hi James, Please perform Sainath's suggestions. I the issue persists, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding. For your convenience, I have list the related link as followed. Windows Home Server Hardware and Installation http://social.microsoft.com/Forums/en-US/whshardware/threads Note: Windows Home Server Hardware and Installation is available. I can READ that forum fine. However, when I go to post a message, the "Ask a Question" page does not offer that forum as a potenial location to post it.Truth, James (http://www.honestillusion.com)

>> we would like to know what happens when you are trying to ping from a local subnet ?This is on my home network, where everything is on the 192.168.0.x subnet, so it is as I describe: Ping OK for 3 minutes, then every packet gets lost or delayed.>> second option is to update the NIC driver , >> try running the below commands It is a headless server, with no keyboard or monitor (doesn't even have a video card). Until I can communicate through the network, the only thing I can do with it is power cycle.Truth, James (http://www.honestillusion.com)

Hi James, Please navigate to Windows Home Server Forum, and initial a post as you did here so that you can get the most qualified pool of respondents. Thanks for your understanding. Best regards, Vincent Hu

I found the problem. I WAS navigating to Windows Home Server Forum. However, I was accidentally going through TechNet. (Hey-- I found the forum through Bing). TechNet lets you read the forum, but not post. Once someone gave me the direct link, everything was OK. Truth, James (http://www.honestillusion.com)