Gordon Ross wrote:
>> If I run "snoop host rosalind" and "smbutil lookup rosalind",
>> I get no snoop output.
>
> That's odd. Did you run snoop on the machine where you're
> trying to use the Solaris CIFS client? You should see something.
Yes.
> Here's a good snoop command line if you want just NetBIOS/SMB:
> snoop -o /tmp/output.snoop port 137 or port 138 or port 139 or port 445
>
> Then use: wireshark /tmp/output.snoop
Where do I get wireshark? It doesn't seem to be part of OpenSolaris.
I did the above; here's the snoop output:
1 0.00000 home-100 -> nissan SMB C Code=0x4 Name=SMBclose
FileID=0x2a38 Error=0
2 0.00098 nissan -> home-100 SMB R Code=0x4 Name=SMBclose Error=0
3 0.10230 home-100 -> nissan NBT C port=1858
4 7.88539 home-100 -> nissan SMB C Code=0x32 Name=SMBtrans2
QueryPathInfo File=\readerware\AWareDB.awd.thumbnails\910.GIF Error=0
5 0.00659 nissan -> home-100 SMB R Code=0x32 Name=SMBtrans2
Error=0
6 0.00049 home-100 -> nissan SMB C Code=0x32 Name=SMBtrans2
QueryPathInfo File=\readerware\AWareDB.awd.thumbnails\910.JPG Error=0
7 0.00284 nissan -> home-100 SMB R Code=0x32 Name=SMBtrans2
Error=0
8 0.15177 home-100 -> nissan NBT C port=1858
9 14.40271 nissan -> home-105 NBT Type=SESSION KEEP ALIVE Length=0
10 0.12333 home-105 -> nissan NBT C port=4204
The first 8 messages occurred before I ran smbutil. The last two
occurred after smbutil failed. I tried again and got no output
during the time I was testing. Clearly snoop is finding the SMB
traffic, but none of it seems to be coming from smbutil.
> The snoop capture is the best way to figure this out.
> You should see NetBIOS name requests from your CIFS client,
> either broadcast, or to the configured WINS, or both.
I'm not seeing it. Am I doing something wrong?
> Trying without punchin running would be a good idea.
I'll try that when I get home tonight.
Is it possible smbutil is confused by having multiple interfaces?
Here's what I have:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
iprb0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255
ether 0:7:e9:d6:88:85
ip.tun0: flags=10010008d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,IPv4,FIXEDMTU>
mtu 1366 index 3
inet tunnel src 192.168.0.2 tunnel dst 192.18.32.151
tunnel security settings --> use 'ipsecconf -ln -i ip.tun0'
tunnel hop limit 60
inet 129.150.12.54 --> 129.145.40.124 netmask ffffffff
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
ip.tun0: flags=1002200851<UP,POINTOPOINT,RUNNING,MULTICAST,NONUD,IPv6,FIXEDMTU>
mtu 1366 index 3
inet tunnel src 192.168.0.2 tunnel dst 192.18.32.151
tunnel security settings --> use 'ipsecconf -ln -i ip.tun0'
tunnel hop limit 60
inet6 fe80::8196:c36/128 --> fe80::1
ip.tun0:1:
flags=1002200851<UP,POINTOPOINT,RUNNING,MULTICAST,NONUD,IPv6,FIXEDMTU> mtu 1366
index 3
inet6 2002:8191:287c:1::8196:c36/128 --> 2002:8191:287c:1::1
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
