\begin{Paul Robinson}
> There's nothing out of the ordinary in the log files. I got tcpdump
> running on the eth0 interface and tried printing to lp and the closest
> that I could find to anything referring to the machine with the printer
> (hilly) is below.
>
> 19:13:46.179207 arp who-has ace.starbug tell hilly.starbug
> 19:13:46.179321 arp reply ace.starbug is-at 0:0:c0:61:5b:96
> 19:13:46.179835 hilly.starbug.netbios-ns > ace.starbug.netbios-ns: udp
> 62
> 19:13:58.458908 0:48:45:80:66:e1 > Broadcast sap e0 ui/C len=43
> ffff 0022 0011 0000 0000 ffff ffff ffff
> 0452 0000 0000 0048 4580 66e1 403c 0001
> 0004 2020 2020 2020 2020 20
>
> I can sort of make sense of it but I couldn't see anything refering to
> say port 139 or there abouts for netbios ports.
(shouldn't that be "holly.starbug" ?)
if you check /etc/services (or run tcpdump with -n) you'll see that
netbios-ns is port 137, the wins port.
you've chopped out a little too much here to be useful, but it does
show hilly answering a wins request (i think), which means that
something got through to hilly.
go through /usr/doc/samba/DIAGNOSIS.txt.gz that will step you through
diagnosing samba/windows networking problems. basically just mess
about with smbclient until things start to work.
--
- Gus
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
