"no logon servers available to service the logon request" issue

We have a single domain network with several remote computers accessing the network via point-to-point wireless or via VPN through DSL. Each remote site has 2-3 computers but no servers - the domain controllers and DNS servers are at the corporate office. They all have domain logins (no local logins). When the point-to-point is up, all is well.....they can all access a certain folder that only resides on only one PC at each remote site. However, when the link goes down, everything quits working. The login takes several minutes to complete, and when they try to access the folder that is on the other PC (but within the same remote site), they get an error: " There are currently no logon servers available to service the logon request". They can't even print to the printer that is local on one of the PCs.

I need each of the remote sites to continue operating within their site even when the link back to corporate goes down. Having no email or Internet is fine during down times, but they have to be able to talk to each PC within their site whenever the link goes down. I can't put a Domain Controller at each site, and I'm running out of ideas. We never had a problem when we used to set up the users to log on locally, but we don't want to go back to that. The link has gone down at least once a day for 3 days straight, and the customers are getting irate. Is it a WINS issue? DNS? Any help would be greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob WilliamsCommented:
As the error message states, there are no logon servers. You users authenticate to your domain controller, when they loose that connection it can take quite a while for the machine to boot up as it is trying to contact it's domain controller and DNS server. Eventually they should boot using cached credential but this can be a little flaky sometimes. Any name resolution through DNS is unavailable and printers in Active directory are unavailable. You could likely elevate a lot of the problems by adding all the local computers to the LMHosts file on the local systems and setting up printers to point directly to the printer, preferably with a TCP/IP port, rather than through Active Directory.
The LMHosts file would allow for local name resolution and works very well, but has to be maintained/updated as changes are made. It will not work if your PC's are assigned IP's through DHCP. You will need to assign them static IP's. You could actually update or overwrite the LMHOSTS file in a login script so it only has to be manually updated in one location.
Where all computers are part of a Domain it becomes a rather tricky situation when no Domain Controller is available.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rob WilliamsCommented:
Thanks classichomes,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.