Unable to access a workgroup computer using VPN

  • Thread starter Thread starter Brad Pears
  • Start date Start date
B

Brad Pears

We have two Win2k servers and one NT 4.0 server in our environment. Our
remote users can access shares on the two Win2K servers which are part of
our domain, but they are unable to access shares on the NT 4.0 server which
is NOT part of the domain currently - it is part of a workgroup right now.

Why would the VPN users not be able to access the workgroup computer the
same as they are able to when they are logged on the network locally? They
logon to the domain locally or through the VPN so I would have thought they
could acces the same resources through the VPN as when they are local.

Is there some additional protocols or settings I need to enable on the VPN
client to allow this?

Any help would be most appreciated!

Thanks,

Brad
 
Is the workgroup name of the server the same as the domain name? This is a
browsing issue and most likely in it's current setup it will not ever work
without either adding it to the domain so that it registers with WINS/DNS or
use a lmhosts file on the clients to find this box OR make sure that your
internal DNS server has entries for this machine. Also make sure your VPN
clients are getting the correct DNS/WINS servers.
 
Thanks Scott. The plan is to get this server into the domain anyway, so
jhopefully that will solve the issue. In the meantime, you mentioned to set
up an entry for it in the internal DNS server.

Where exactly would I set that up and would that then work?

Thanks,

Brad
 
Is this a NT4 domain or a Wind2k/2k3 Active Directory Domain? If NT4 then
DNS will not be necessary if 2k/2k3 then DHCP should hand out the ip of your
internal DNS server to your remote clients.
 
It is a Win2K domain. I assumed that the remote clients would get the DNS
server through DHCP - and this is why I am confused as to why they cannot
access the NT4 box that is in the workgroup. Internally, I have our DHCP
server set up to give out DNS name and the firewall also knows the IP of the
DNS server. Maybe the remote clients are not getting the DNS from where I am
thinking they should. When they connect to the firewall, the remote clients
are given an IP address in teh pool I have specified. However, who would
give them the DNS Ip address? SHould it also be the firewall?
 
Back
Top