• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

vpn/domain issues with windows 2003

P

pcthuglife

Member
Hello,
I am having a strange problem and have not been able to find an answer yet:

We have a windows 2003 domain using active directory. Users browse PCs on the domain by typing in \\domainname and then are able to see all PCs on our network.

As soon an I turn on routing and remote access (I use for VPN) local users are not able to browse by going to \\domainname - none of the PCs on our network show up. If I disable routing and remote access and then browse to \\domainname all of our local PCs show up again.

Does anyone know what is causing this and how to fix?
Thanks Much
 
First thing I'd check is to run "IPConfig /all" on one of the client PCs and see where the DNS Server and WINS Server are pointed.

Is your Windows 2003 Server the Default Gateway and DHCP Server for your client PCs?

Finally, \\domainname would normally list shared folders, not networked computers.
 
for our local "lan" clients, the domain controller is the primary dns server. we have a linux firewall that acts as the default gateway. or were you inquiring about the settings for the vpn clients?
 
I'm not sure if this is related, but I'll spit it out there...

On our 2003 Box, we have it setup as a secondary DNS server for our primary, which is a 2000 Active Directory server. Everything works fine until I enable the Routing And Remote Access service on the 2003 box. At that point, for some reason, one of the servers (im thinking the 2000 box) refuses to update the DNS on the 2003 box with RRAS enabled. I have no idea why, and its causing me quite the hastle. DNS is b0rked then and clients cannot resolve local dns addresses.

Hopefully theres a reason for this!
 
Originally posted by: pcthuglife
for our local "lan" clients, the domain controller is the primary dns server. we have a linux firewall that acts as the default gateway. or were you inquiring about the settings for the vpn clients?
Click to expand...
I meant your local LAN clients. I was just trying to get an idea of where your various directory services were located.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top