The fact that they can open the share under the same login at work makes me
think the problem is more likely name resolution that permissions
(particularly with WINS and NetBIOS blocked). Can a share be mapped using a
command like "net use X: \\192.168.1.1\sharename"? Does "net view
\\192.168.1.1 return an error code (it should list shares)? If so, error 5
tends to indicate a permissions issue and error 53 a name resolution
problem. I hope this is of some use in narrowing it.
--
Josh said:
here's a little more detail... win2k pro server. netscreen 5gt firewall
w/ netscreen remote software (by safenet) this manages the IPsec VPN. The
laptops are on XPpro, sp1. The users log into the domain with their
usernames and passwords at logon in the office w/ no problems. Mapped
drives are set to the IP of the server as the VPN is not setup for WINS
passthrough. Offsite, the activate their VPN software, and when they send a
request to the server, both the laptop and the firewalls logs show a
complete session. Now, when they attempt to open a mapped drive through the
VPN or open \\192.168.1.1 they get a message that says they can not connect
to the mapping. It appears to be a sharing problem or a permissions issue,
wasn't sure where to appoach from.