[Gordon Currie]

I have a HP EX485 running the HP 3.0 software on WHS PP 3. I've never had a problem in the last 18 months with connecting to my WHS either with the Console or through RDP.

Somehow since last Thursday afternoon, my WHS box is randomly losing connection to the LAN. It shows up in my Network, but I cannot access it. RDP or Console will not connect. I have to resort to a hard power down/power up to get the server responsive again.

During this, the lights on the server are blue (good), no problems reported.

No software has been installed in the last month, other than possibly Windows updates.

When it is unresponsive, I can still ping the server successfully.

I do notice that in my event logs, the server does NOT appear to be going to sleep anymore (4 am to 6 am), even though the Server Sleep setting is active. This is new, but I'm unsure how long it might have been going on.

There are no unusual errors/warnings in the event logs.

Any ideas?

[Garry]

Gordon Currie, on 05 July 2010 - 06:47 PM, said:

I have a HP EX485 running the HP 3.0 software on WHS PP 3. I've never had a problem in the last 18 months with connecting to my WHS either with the Console or through RDP.

Somehow since last Thursday afternoon, my WHS box is randomly losing connection to the LAN. It shows up in my Network, but I cannot access it. RDP or Console will not connect. I have to resort to a hard power down/power up to get the server responsive again.

During this, the lights on the server are blue (good), no problems reported.

No software has been installed in the last month, other than possibly Windows updates.

When it is unresponsive, I can still ping the server successfully.

I do notice that in my event logs, the server does NOT appear to be going to sleep anymore (4 am to 6 am), even though the Server Sleep setting is active. This is new, but I'm unsure how long it might have been going on.

There are no unusual errors/warnings in the event logs.

Any ideas?

********************
Only one option here. Reinstall.

[Gordon Currie]

Garry, on 06 July 2010 - 01:00 AM, said:

********************
Only one option here. Reinstall.

Thanks for the response. I just did a System Restore when I installed HP 3.0 software 5 weeks ago. You mean I have to do it again? Hmm.

[hiitsjack]

Gordon Currie, on 06 July 2010 - 04:10 AM, said:

Thanks for the response. I just did a System Restore when I installed HP 3.0 software 5 weeks ago. You mean I have to do it again? Hmm.

I'd try re-installing the connector software on your client.

After you have re-established connection to your server (as you mentioned by re-booting the server).

1. On your client PC - Open windows explorer.
2. goto your server.
3. Then "Software".
4. Then "Home Server Connector Software".
5. Then double click on the "setup" application file.

The "setup" application file will then un-install the existing connector software and then re-install it (ensuring you have the version that matches your server version).

Jack

[Gordon Currie]

As a follow up to my issue, I was able to get things working reliably again by changing the NIC driver settings so that Flow Control and all Offloading settings were OFF. I thought I had changed those earlier; maybe they were reset after a driver update...

I also saw one Iastor driver error, so I updated that as well.

5 solid days of uptime, looks fixed.

[rascaluk]

Gordon Currie, on 19 July 2010 - 10:35 PM, said:

As a follow up to my issue, I was able to get things working reliably again by changing the NIC driver settings so that Flow Control and all Offloading settings were OFF. I thought I had changed those earlier; maybe they were reset after a driver update...

I also saw one Iastor driver error, so I updated that as well.

5 solid days of uptime, looks fixed.

I've started having the same prob over the last week or so on my homebuild WHS. Gonna have a poke around in the NIC settings now. Fingers crossed.

Even when it appears to be up, copying any sizeable file across the network to it resuls in a fail halfway across.

[zuz242]

Gordon Currie, on 19 July 2010 - 10:35 PM, said:

As a follow up to my issue, I was able to get things working reliably again by changing the NIC driver settings so that Flow Control and all Offloading settings were OFF. I thought I had changed those earlier; maybe they were reset after a driver update...

I also saw one Iastor driver error, so I updated that as well.

5 solid days of uptime, looks fixed.

similiar problem with my intel ss4200 whs server: it loses outside (internet) connectivity afer some while. internal net connection remains ok, whs outbound ping (www.google.com) is working still.
i did try to change the nic settings but the error still occurs ...

btw. got a iastor error as well