authenticate clients over router to router VPN ?

[scott]

Hi,

- I have an NT4 server at site A and various windows clinets at site B.
- I have used routers to connect each site using vpn, the conneciton exists
24/7.
- I wish to map a drive from the clients at B to the server A.

1. What is the best way to authenticate the remote clients on the remote NT4
domain to allow them to access the share / mapped drive ?

i.e
- should i just allow EVERYONE access to the share and therefore i should
not be prompted for user + pass ?

2. In order to map a drive over this network, how can the clinets find the
network share after the router to router vpn link is established ?

i.e
- enter a static router in the router pointing to remote subnet ?

Thanks
Scott.

 

[Bill Grant]

If the site to site VPN link is correctly set up, a client in one site
should be able to ping any machine in the other site by IP address. That is
controlled by the static routes on the VPN endpoints. If you can't do this,
you don't have a true site to site VPN.

Name resolution and domain login area separate problems. Are you running
WINS? Can the clients ping the server by name? Are the clients configured to
do a domain login?

 

[scott]

Hi,

Thanks for the reply. In this scenario im assuming i have a site-to-site vpn
connection established i.e can ping etc..

Im just trying to get my head around the share authentication method ?

i.e the routers establish the connection, the clients at the remote site can
ping the server, they are not part of the domain.

I want to make it as easy as possible for these remote clients that are not
part of the domain to access a network share - ie. without user + pass if
possible. What happens when a clinet machine maps a drive and are not part
of the domain I guess is my question ? (can test it on the lan i guess).

Just trying to get my head around the concept before suggesting a method of
setup.

Sorry for the ambiguity.

Thanks for your reply.
Scott.

 

[Bill Grant]

If the site-to-site is working, the setup is basically just like two
subnets connected by an IP router (a slow one!). Because of the router,
broadcasts don't work. So you need DNS or WINS to get name resolution
working. Once you get WINS running across the link, browsing should also
work.

Clients who are not domain members can share files as long as their
credentials are valid on the domain. Remote access and VPN dialup clients do
it all the time.