OBESEJESUS
asked on
Windows Home Server SP2 constantly drops network shares
Windows Home Server SP2 drops the folder shares every once in a while, there's no rhyme or reason. I have changed out the NIC several times, updated the NIC's driver several times, updated Windows several times, made config changes to the router several times, swapped out the only single switch on the network twice.
The problem really happens at random, it'll just close the shared folders that are open and disconnect the user from those shares.
Trying to ping from the server to the client while this is happening results in nothing getting through from server to client. AFAIK, it's the same way when going the opposite direction.
Server has a static IP NOT in the DHCP range that it hands out, it is a reserved IP within DHCP for the server and its MAC address.
There is literally nothing in the event viewer when things like this happen. There was an indication that the NIC was being disconnected and that was the reason I changed it out to no avail.
From Google searched I can clearly see that Windows Home Server has a ton of issues with the network shares being disconnected and or itself just completely disconnecting from its users/clients.
Any ideas?
The problem really happens at random, it'll just close the shared folders that are open and disconnect the user from those shares.
Trying to ping from the server to the client while this is happening results in nothing getting through from server to client. AFAIK, it's the same way when going the opposite direction.
Server has a static IP NOT in the DHCP range that it hands out, it is a reserved IP within DHCP for the server and its MAC address.
There is literally nothing in the event viewer when things like this happen. There was an indication that the NIC was being disconnected and that was the reason I changed it out to no avail.
From Google searched I can clearly see that Windows Home Server has a ton of issues with the network shares being disconnected and or itself just completely disconnecting from its users/clients.
Any ideas?
Bud Durland
Check the power settings for the server & for the NIC. There's a n option "Allow system to power down this device" (or similar) in the NIC properties. Be sure that it is NOT checked. Also, have you mad sure you have the latest drivers for the NIC? WHS is basically server 2003, so drivers for that OS will work.
So if i understand this IP assigned to the MAC isnt part of DHCP ?
At that time are you able to do Nslookup with teh NBIOS of the machine or check its share with NBIOS or FQDN ?
How many NIC's are there on the affected server .... i mean where the share resides ?
- Rancy
At that time are you able to do Nslookup with teh NBIOS of the machine or check its share with NBIOS or FQDN ?
How many NIC's are there on the affected server .... i mean where the share resides ?
- Rancy
ASKER
The server is a single server with a single NIC. We are now using a USB 10/100 NIC. Also the power saving mode is indeed disabled.
I have indeed made sure it is the latest available drivers.
The IP assigned was well below the DHCP scope I set on the router.
However, after doing some searching I found someone with a similar problem who indicated that it was a problem with DHCP and that reserving the actual IP solved the problem.
So I went back, changed the DHCP range from 5-25 and made sure that the 192.168.1.5 IP was reserved and had its MAC address added to the reservation.
It'll be a wait and see thing now.
I have indeed made sure it is the latest available drivers.
The IP assigned was well below the DHCP scope I set on the router.
However, after doing some searching I found someone with a similar problem who indicated that it was a problem with DHCP and that reserving the actual IP solved the problem.
So I went back, changed the DHCP range from 5-25 and made sure that the 192.168.1.5 IP was reserved and had its MAC address added to the reservation.
It'll be a wait and see thing now.
Hummm .... please keep me updated so if need i can jump in the party :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>>It looks like the server's IP needed to be put into the DHCP reservation range.
I do not think so... how many IP addresses in your DHCP range?
"Windows Home Server SP2" "HOME" version? Supposed that HOME version allows 10 concurrent connections only. Some connections should be dropped when it's over 10. It is one of big reason why the HOME version price is cheaper than Standard or Enterprise versions.
I do not think so... how many IP addresses in your DHCP range?
"Windows Home Server SP2" "HOME" version? Supposed that HOME version allows 10 concurrent connections only. Some connections should be dropped when it's over 10. It is one of big reason why the HOME version price is cheaper than Standard or Enterprise versions.
ASKER
There are five people total that connect to it. No more no less. I can see the connections in the appropriate msc. So far so good
For Windows XP Professional-based computers, the maximum number of concurrent network connections that are allowed is 10. This limit includes all transfer and all resource share protocols. For Windows XP Home Edition-based computers, the maximum number of concurrent network connections that are allowed is 5. This limit is the number of sessions that can be hosted at the same time from other computers
Furthermore, any error log from HOME Server?
e.g.
Operating system error 71.
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
Info:
Troubleshooting Server Message Block inbound connection limit in Windows peer-to-peer workgroup
http://support.microsoft.com/kb/328459
Furthermore, any error log from HOME Server?
e.g.
Operating system error 71.
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
Info:
Troubleshooting Server Message Block inbound connection limit in Windows peer-to-peer workgroup
http://support.microsoft.com/kb/328459
ASKER
No error messages in event viewer logs. I believe we fixed it. If problem returns next step is new server with sbs.
ASKER
I found the answer via Google searching.