Welcome to WebmasterWorld Guest from

Forum Moderators: bill

Message Too Old, No Replies

server 2003 share time out

server 2003 share time out

7:48 pm on Sep 13, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:May 16, 2003
votes: 0

My office computer network is made up of a server running windows server 2003, and PCs all running XP.
Individual PCs log on to the server and are able to use shared resources like folders and printers etc.

The problem I have is once a person logs in they can access all shares, but as time passes they loose permission to access shares on the network.
The only way to get permission back is to log out and log back in again.

I have checked a ton of settings on both the server 2003 and XP, changing all of the ones that timeout to a week or 2, but this problem just won't go away.
Has anyone else had this problem?

6:40 am on Sept 27, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
votes: 131

Sorry, it doesn't sound like anyone else has experienced this. I'm just bumping this thread back up to the top to see if anyone can lend a hand.
1:48 pm on Sept 27, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:Nov 29, 2002
votes: 0

Just a guess that you can check out...

I've seen cases when the DHCP client on an XP box will tear down the entire TCP/IP stack at 50% of the lease time exactly to perform its lease renewal. Moreover, this client will always attempt to get a new lease everytime it starts, even if it still has "time" on the lease it previously held.

When that happens, all active connections are dropped, including shares, and the mapped drive connections will appear as "disconnected network drive" in My Computer until they are clicked on again.

It would be interesting to check the disconnects against the DHCP lease time to see if there's a correlation.

There are also timeouts for NetBIOS connections -- What settings have you tweaked? -- I've always has more success using a protocol like IPX/SPX over TCP/IP on a LAN because TCP connections are incredibly sensitive to timeouts. Moreover, the TCP/IP settings that would work well over the internet and your LAN may not be the best settings to use for shares, so you may have to strike a compromise to get the results you want. Keep in mind that if you are using NetBIOS over TCP/IP that the TCP settings may override or conflict with the NetBIOS-specific settings.

Lastly -- Networking: Firewalls on the PCs may be blocking essential network level broadcasts and other communications that the PCs need to make to stay connected to each other. On that same token, some switches/hubs do not properly forward/flood MAC level broadcasts in an attempt to prevent broadcast storms. So check your "security" options.

11:06 pm on Sept 27, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:May 16, 2003
posts: 167
votes: 0

BILL Thanks for bumping this back up, Im still struggling with this.


I have not looked into the areas you have mentioned except fire walls on the pc.
I do not run fire wall on our PCs. I will take a look thanks!

First I checked all my shares and users making sure everything was wide open, full permission, fully shared.
I looked for any timeout seating for user and computer accounts, polices, user groups etc on server 2003.

I then turned off autodisconnect using net config server /autodisconnect:-1 on all pcs and server.

I'm still losing the shares but they seem to be accessible for longer. I will definitely take a look at what you mentioned above, I really appreciate it!

just some more information, this problem only occurs with users that belong to the network domain. Users that just log on locally to PC
and have permission to access shares never loose access or permissions. It seems once the user joins the Win Server 2003 domain
is when the idle timeout start occurring.