Mac OS X: tunnel OK, ping works, but no SMB connectivity
I am using the VPN client for Mac OS X to connect to our corporate network. The problem that I have is that after starting the VPN connection (configured for split tunneling) I can ping the WINS server, but can't use it to resolve WINS names:
[localhost:~] admin% ping 10.20.1.10
PING 10.20.1.10 (10.20.1.10): 56 data bytes
64 bytes from 10.20.1.10: icmp_seq=0 ttl=127 time=28.909 ms
However, for whatever reason I can't query the WINS server:
[localhost:~] admin% smbutil lookup fr2
smbutil: can't get server address `10.20.1.10':
smbutil: can't resolve 10.20.1.10: syserr = Network is down
This is after I supplied the WINS server address in a file ~/.nsmbrc:
What could be wrong? Would there be a problem with the Mac OS X machine being behind a NAT router connected to a cable modem? Having the cable modem ISP block port 80 shouldn't be a problem, should it?
I do recommend that you do open a case on this though, this may take some testing in the laboratory.
In regard to the vpnclient and tracking where the packets are going can you grab the "vpnclient stat" command check where the packet count is encrypting, I think we may find that it is being "bypassed" rather then sent down the tunnel.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...