This is a long-standing problem if the server is a domain controller,
especially the first/only DC in the domain/forest. As soon as the first
remote client connects, the server becomes multihomed (because it acquires
an extra IP for the internal interface).
This upsets the browser service. If you are using DDNS, it can also upset
DNS related services. See KB 830063 .
<(E-Mail Removed)> wrote in message
news:1d94401c4547b$9ed498e0$(E-Mail Removed)...
> We have 2 NICs in our server, one dedicated to the LAN
> the other is dedicated to VPN. I set up the VPN on the
> Windows 2003 server and it works great except for one
> problem. After a user establishes a VPN connection no one
> on the LAN side can browse the network. We get an error:
>
> "Domain is not accessible. You might not have permission
> to use this network resource. Contact the system
> administrator of this server to find out if you have
> access permissions.
>
> Windows cannot find the network path. Verify that the
> network path is correct and the destination computer is
> not busy or turned off. If Windows still cannot find the
> network path, contact your network administrator."
>
> Does any have any ideas that could help me???
>
> Thanks,
> Ryan
|