Specifics first: Shrew 2.1.7 on Win7 (32 or 64 bit) with PCF imported from old
Cisco client.
Samba server destination: Redhat 8 with samba 2.2.5 (yes, it’s old and that’s
probably most of the problem).
The Win7 client can make a successful Shrew VPN connection to the network and
ping network resources and can access Samba shares on all servers EXCEPT the
one above. It can get to port 80 on that server and also SSH without a problem.
The Win7 (32-bit) client running the Cisco client can successfully get to the
shares on the server above...as well as port 80, etc.
This is an issue because 64-bit Cisco client is unavailable (and probably
wouldn’t work with the PIX firewall anyway), so Shrew “is the ticket” for the
64-bit Win7 users, but they MUST be able to access the samba shares on that one
server.
When Shrew is used, there is no indication in the Samba logs that an attempt
was made to connect to the share. On the client, you put in \\xx.xx.xx.xx\share
in the Computer window and after about 20 seconds, the message is given that
the server\share cannot be contacted (check spelling of name, etc.). If you
attempt to map a network drive to it, you get a username/password dialog but it
doesn’t matter what you put in there.
Why would the Cisco client work but the Shrew one does not? What am I missing?
Carl Hilinski
Systems Director
9 E. Market St.
Leesburg, Va. 20175
703-777-1111 ext. 1359
703-669-3008 (direct)
703-771-0036 (fax)
www.TimesCommunity.com
[email protected]
_______________________________________________
vpn-help mailing list
[email protected]
http://lists.shrew.net/mailman/listinfo/vpn-help
