On 05/25/2012 12:26 PM, Eric W. Bates wrote:
You get to blame MS for that one.
See if you can connect using IP addresses. Name resolution in Windoze is
handled in a variety of ways depending on what version of Windows you
are running and whether you have a domain controller or a WINS server.
Bottom line: name service in Windows is weak at best.
If the IP connection works for you, there are a number of remediations
you can try to fix the name service issue. But to some degree, that's
really a separate issue from building a working IPSec tunnel.
On 5/25/2012 5:59 AM, [email protected] wrote:
I can enable the tunnel but I can not map any drives or connect to the
host
computer. I do see the "Local area connect * 9" using the shrewsoft
virtual
adapter. Under the network and sharing Center when trying to show a map I
get "Windows can not discover any compter or device". I tried the 30 day
trial version of Greenbow and it worked fine.
I have seen others with similar problems but no solution.
Hi Dennis, here's some suggestions, assuming you're still having the
problem.
I would first suggest you use the Shrew 2.2.0 beta client (if you're not
already). It has a number of enhancements that may help. At the very
least, it has better support for Windows 7 than Shrew version 2.1.7 does.
I would also have you check to ensure that that "Enable WINS" is checked
on the "Name Resolution" tab in the Access Manager Site Configuration.
You could also generate a log file so we could see if WINS server
details are being provided as part of the connection negotiation process:
http://www.shrew.net/support/wiki/BugReportVpnWindows
_______________________________________________
vpn-help mailing list
[email protected]
http://lists.shrew.net/mailman/listinfo/vpn-help
