Also bear in mind that the credentials you supply to set up a VPN have
nothing to do with accessing files shares. When you log on to a machine, you
supply credentials which are checked by your local machine or a domain
controller (or you may log on with cached credentials if you were previously
logged on to a domain but a DC is not currently available)
These are the credentials which will be used to grant you access to
shares on other machines. If you later connect by VPN to another network and
need to supply other credentials, these are used solely to authenticate the
connection. They do not alter the credentials used to validate file access.
"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> I am a bit confused by this. If the router is handling the VPN
> connections, why do you have two NICs in the Windows server? And why are
> you trying to configure the server as a remote access server? If you want
> the Windows server to handle the authentication for the VPN connections
> you only need IAS set up on the Windows server, not RRAS. And you only
> need one NIC.
>
> "Mauro" <(E-Mail Removed)> wrote in message
> news:9D35F4BF-C2DD-418E-ADB4-(E-Mail Removed)...
>>I have a 2003 server with two NIC, one on our internal network IP, one
>> configured as 192.168.7.7
>>
>> I have also setup the Lan side of the router to our internal IP and
>> 192.168.7.2, this router handles all the VPN tunnels directly, meaning if
>> I'm
>> at a remote location and I enable the VPN certificate it connects me
>> directly
>> to internal network.
>>
>> I setup the remote access and routing as VPN with 10 of our internal IP
>> address as a range and 192.168.7.7 as the VPN connection.
>>
>> Is there anything else I'm missing to be able to authenticate to our main
>> server on our internal network IP and use it's shared folders as if I was
>> on
>> the network?
>>
>> Regards,
>> Mauro
>>
>
>
|
Similar Threads
Linear Mode
