"Jeff Richardson" <(E-Mail Removed)> wrote in
message news:F43C01C0-6400-4F61-86F4-(E-Mail Removed)...
> We have a user who will be connecting from a remote office via a VPN to
our
> main office. THe server running RRAS is a windows 2003 server. We're
> testing the VPN cnnection and the connection is established & Connected
with
> no errors, however the remote workstation can't acces any network
resources -
The credentials for the VPN Connection do *only* that,...they create the
connection,...they do *not* log you into the Domain.
> IP addresses are assigned via DHCP - the remote connection gets assigned
an
> IP address - this ip resolves from the RRAS server but for all other
server /
> workstations if we attempt to PING to connected workstation by name we get
a
> different IP address
I have no explaination for that,...although I don't really understand what
you are decribing,...you need to be more precise.
Keep in mind that the VPN client needs to get more than just the IP#, Mask,
Gateway, when they connect. They also need to get the WINS Server and the
DNS Server from the Target LAN. WINS is highly recommended. You can even
statically assign them to the connection on their machine if you don't want
to fool with DHCP for that part of it.
The VPN Client also needs for their machine to be member of the Domain if
they expect full Domain access as if they were physically sitting on the
LAN. When at the Crtl-Alt-Del prompt of their machine they need to check
the box that says "Log on using Dialup Connection" and choose the proper VPN
Connection when prompted for it. The credentials for the Connection do not
have to match the normal Domain credentials, but both will be required for
full normal access.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
Similar Threads
Linear Mode
