(1) Domain is not accessible: this is computer browsing over VPN issue. It is better to have a WINS server since you already have the Domain.
2) Lost of Intranet: this is another perfect example of enabling VPN on a DC.
http://www.howtonetworking.com/cases...dcdnswins1.htm should help.
please keep us update.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"xfile" <cou-(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Hi,
Got another question and hope someone could help us.
We finally made a VPN connection with dial-up connection from XP Pro to Win
2003 Server (serves as DC and VPN server) using the custom installation
wizard with only one NIC.
The issues that we experienced are:
(1) Domain is not accessible: When we clicked the domain name in My Network
Places, we got an error message " xxx is not accessible. You may not
have..." But we could use the mapped shared folders to copy from the shared
folder and to the connected client's folder.
(2) Lost of Intranet: After many tries, it seems that as long as VPN has
been set up (with whatever types), the intranet will be lost. That means
all existing trust relationships between client computers and the domain are
gone. And some client computers won't be able to browse. Why is this.
We also found an "possible" solution from here:
http://www.howtonetworking.com/cases...dcdnswins1.htm
Would this be the solution for us?
Many thanks.