On Mon, 16 Feb 2004, Phillip Hellewell wrote: > P.S. You tried ethereal or tcpdump or anything to see what the network > traffic looks like?
k, I have now! When Linux Box tries to access Samba Share, the machines appear to be talking properly--they send across TCP packets all lovely-like and communicate in a proper fashion, something like this: Source Destination Protocol Info 192.168.0.10 192.168.0.183 SMB Negotiate Protocol Request 192.168.0.183 192.168.0.10 SMB Negotiate Protocol Response etc. etc. When Windows Box tries to access Samba Share, the only packets Ethereal shows with Windows Box as the source look like this: Source Destination Protocol Info 192.168.0.199 192.168.0.255 NBNS Name query NB MYCOMPUTER 192.168.0.199 192.168.0.255 NBNS Name query NB MYCOMPUTER 192.168.0.199 192.168.0.255 NBNS Name query NB MYWORKGROUP (with the latter repeated about a dozen times) please note that the Samba Share is on 192.168.0.183. I have no idea who 192.168.0.255 is, or why Windows Box (199) is trying to talk to him. The Samba Share box (183) doesn't send any packets to Windows Box (199). Ross -- This sentence would be seven words long if it were six words shorter. ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
