Hi, I using Samba on a Linux system (Fedora) to provide a simple share (using SHARE security). I use te share for storing files and swapping files between different systems (WinXP and Win98). I have no trouble connecting to the system (using search computers and than providing the NetBIOS name or mapping drives), but the system refuses to show in the Network Neighborhood or under My Network Places. Now I have been experimenting with some settings. Deploying a Laptop (Fedora Core 2/Samba 3.06) within the simple network (single Ethernet segment) and configure the Laptop to become the WINS server and to win the browse election. Makes both systems visable in the Network neighborhood. When my original system is Wins server and domain-master then no other system is visable in the Network Neighborhood. Having traced both situations with Ethereal, i have found this: In a good situation is see No. Time Source Destination Protocol Info 667 180.748866 172.18.1.99 172.18.1.82 TCP 4771 > netbios-ssn [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1460 668 180.748896 172.18.1.82 172.18.1.99 TCP netbios-ssn > 4771 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 669 180.749877 172.18.1.99 172.18.1.82 NBSS Session request, to DELL-5151-JWH<20> from DELL-8100<00> 670 180.749907 172.18.1.82 172.18.1.99 TCP netbios-ssn > 4771 [ACK] Seq=1 Ack=73 Win=5840 Len=0 671 180.790282 172.18.1.82 172.18.1.99 NBSS Positive session response 672 180.795916 172.18.1.99 172.18.1.82 SMB Negotiate Protocol Request 673 180.795944 172.18.1.82 172.18.1.99 TCP netbios-ssn > 4771 [ACK] Seq=5 Ack=210 Win=5840 Len=0 674 180.796374 172.18.1.82 172.18.1.99 SMB Negotiate Protocol Response 675 180.798490 172.18.1.99 172.18.1.82 SMB Session Setup AndX Request, User: anonymous; Tree Connect AndX, Path: \\DELL-5151-JWH\IPC$ 676 180.803660 172.18.1.82 172.18.1.99 SMB Session Setup AndX Response; Tree Connect AndX 677 180.804952 172.18.1.99 172.18.1.82 LANMAN NetServerEnum2 Request, Domain Enum 678 180.805289 172.18.1.82 172.18.1.99 LANMAN NetServerEnum2 Response 679 180.810136 172.18.1.99 172.18.1.82 SMB Tree Disconnect Request In the fault situation i see: No. Time Source Destination Protocol Info 56 39.053859 172.18.1.254 172.18.1.82 NBNS Name query response NB 172.18.1.254 57 39.335998 172.18.1.82 172.18.1.254 TCP 32926 > microsoft-ds [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=11941427 TSER=0 WS=7 58 39.337389 172.18.1.254 172.18.1.82 TCP microsoft-ds > 32926 [SYN, ACK] Seq=0 Ack=1 Win=5792 Len=0 MSS=1460 TSV=3867926 TSER=11941427 WS=0 59 39.337413 172.18.1.82 172.18.1.254 TCP 32926 > microsoft-ds [ACK] Seq=1 Ack=1 Win=5888 Len=0 TSV=11941429 TSER=3867926 60 39.346493 172.18.1.82 172.18.1.254 SMB Negotiate Protocol Request 61 39.347927 172.18.1.254 172.18.1.82 TCP microsoft-ds > 32926 [ACK] Seq=1 Ack=184 Win=5792 Len=0 TSV=3867927 TSER=11941438 62 39.351637 172.18.1.254 172.18.1.82 SMB Negotiate Protocol Response 63 39.351648 172.18.1.82 172.18.1.254 TCP 32926 > microsoft-ds [ACK] Seq=184 Ack=100 Win=5888 Len=0 TSV=11941443 TSER=3867928 64 39.352088 172.18.1.82 172.18.1.254 SMB Session Setup AndX Request, User: HOME-NET\root 65 39.370081 172.18.1.254 172.18.1.82 SMB Session Setup AndX Response 66 39.370183 172.18.1.82 172.18.1.254 SMB Tree Connect AndX Request, Path: \\172.18.1.254\IPC$ 67 39.381954 172.18.1.254 172.18.1.82 SMB Tree Connect AndX Response 68 39.382098 172.18.1.82 172.18.1.255 NBNS Name query NB <01><02>__MSBROWSE__<02><01> Now I am not an expert on this, but i find it strange that instead of using the NetBIOS name, now the Path is using an IP address (the correct one). Everytime is see an IP addres instead of a NetBIOS name, i get back an empty browslist. Maybe the use of IP-addresses is correct (for example using a multi-homed system), but I think that the system then also should provide the browselist. If i can be of any assistance just ask, Kind regards Jan Willem Huijbers
Please retest against a current Samba release and reopen if the issue is still present.