Assuming she can ping the remote pc, she may need to cache the credentials by using net command. I have another case in this link,
Can access remote computer via VPN occasionally The username that we use to test can access the remote computer all time. 3. When we can't access the remote computer via VPN, we use net view command to ...
www.chicagotech.net/casestudy/vpnaccess1.htm
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Pablo" <(E-Mail Removed)> wrote in message news:0E645C30-FD73-4B60-BDF1-(E-Mail Removed)...
Hi Robert,
Thanks for your reply.
Both places, i.e. LAN and remote location, have the same IP range
(192.168.1.0/24). However, I do not think this is the issue because when the
user initiates a VPN session from the local computer account everything works
fine. The only "inconvenience" is that she has to send credentials when
trying to access resources on the LAN. For example, when she types
\\server\shareddocs on "My Computer" a pop up window will ask for her
username and password. All she has to do is type in her AD username and all
is fine.
But, when she initiates the session from her AD account (at home she does
the CTRL-ALT-DEL sequence and types her AD user to get to her desktop and
from there she connects to the VPN) none of the resources are available. The
only difference between these two scenarios is the account she is using.
Nevertheless, just to make sure the IP range was not the culprit, I changed
her home addressing to 192.168.2.0/24 (the office remained with
192.168.1.0/24). As you might be guessing, the problem continues: no access
to server resources when using her AD account to connect from home.
Is it possible that her account is somehow blocked?
Regards,
Pablo.