What is strange is some machines drop their mapped drives (quick double click to reconnect the drives but awful and damaging for all who connect to databases), these machines also drop shared printers (doesn't reconnect as gracefully, will say theres a printer issue for a few solid minutes first before one can print). Yet some machines, same computers (Optiplex 780s for Win7, 760s for XP machines) run perfectly fine (so can't be hardware/drivers) One of the machines that drops mapped drives is connected to a Samba server running RHEL6, this could be a samba issue, but then I have another client connecting to samba on RHEL5 and its fine To throw another monkey wrench in, win7 mapping to shared XP drives on an XP Pro machine loses its mapping more often than the samba computer! and win7 mapping to a shared XP Pro printer does the same, this happens variable between 5min and an hour, the Samba connecting one loses connection about twice a day. I have scoured forums, wikis, and there seems to be no concrete result (hence this being my first post), from replace your router (which really makes no sense) to various local policies, registry entries, and sharing/device settings What I have tried: Autodisconnect to an obscene number, (65,356) to 0 and to -1 Keepconn, didn't do anything LanManager, net config server/workstation 128 bit versus 48/56 bit security turn off power savings on NIC disable MS Security Essentails disable Firewall Static IP versus DHCP Homegroup toggle off and on The only thing i can think of is maybe some computers haven't been kept up to date as the earlier win7 machines that i've deployed seem fine, and the new ones (always update before install at a client) that have been fully updated have issues I'm not willing to put these on a domain (many of these outfits are 4-5 machines, nonsensical for a domain) What I haven't tried, mainly due to needing more info, is I want to change all network settings in terms of authentication, connection, methods, etc... to be the same exact way XP does it, (NTLMv2 to NTLM?) but I don't know what to set, in my mind this seems to be the definitive way to fix it... Any ideas? This is a widespread issue with win7 and vista as well. The only thing thats different on these installs are how up to date they are when they were put in, beyond that the differences are minor QBES to EZClaim to eClinicalWorks, to others, but even within these minor differences some machines connect some are finicky Thanks -Carl