Hello,
First, I'll admit I don't think I know as much as I hoped or thought I did about VPN's or networking over them. Which brings me here.
I set up a VPN network to share info from the server at Office A to small Office B (2 workstations).
I'm not sure what all may be important, so if I give too many details, forgive me, but in my experience here, most people helping are always asking posters to give more information or details, so here goes:
Office A -
Windows 2000 Server
Linksys / Cisco VPN Router Model BEFVP41 version 2
Comcast Business Internet
IP's - 192.168.2.X series
Office B -
Both workstations - Windows 2000
Linksys / Cisco VPN Router Model BEFVP41 version 2
Verizon Business DSL
IP's - 192.168.3.X series
When I first established our "tunnel", everything worked great, including roaming profiles. As time goes on, more and more problems.
1. Users could get on internet, but not access server folders.
2. Fix folder problems, internet would not work.
3. Eventually it boiled down to roaming profiles stopped working.
That is a VERY abreviated version of what leads me here today.
The administrator logon never (knock on wood) has a problem. I have one user that is a domain admin, but cannot access her user folder, so I'm confused why the admin can always log on the same machine and NOT experience problems?
I probably have everything pretty well screwed up now, as like most techs, I Google for answers and try many things. Both the server and all workstations in the network are running Windows 2000 with SP4. I read that SP4 may be a coulprit in a couple posts elsewhere; I reformatted a machine and only put SP3. I can't get the roaming profile to work with SP3 either, so I'm think the service pack has nothing to do with anything now.
This week, I created a user name that uses a local profile, with the same rights as the main user I mentioned above with domain admin rights has. For Day 1, everything worked great! Today, same problem as she had before:
An error occurred while reconnecting S: to \\<servername>\users\sales
Microsoft Windows Network : There are currently no logon servers available to service the logon request.
This connection has not been restored.
I can drop to a DOS window and type "ping <servername>" and it reports the corrent IP address with excellent ping time.
I can ping the IP address, with same results.
I cannot browse the network going through My Network Places either.
I *CAN* connect to each workstation over the VPN using pcAnywhere from Office A.
I *CAN* connect to the server using Term Services from Office B.
Obviously, this is working to some degree. I'm sure there is still information you'll need. Just ask.
If I can get 1 or 2 experienced techs to help resolve this, I am willing to post some related follow up questions you can answer for more than the 500 points I can post at one time here.
Thanks,
Loral
