I've just upgraded my SuSE 9.0 machine to SusE 9.3 and something has gone wrong with my samba functionality. Under SuSE 9.0, my machine worked great as both a samba client and a samba server. Now that I've upgraded I have a strange problem as a samba client. I find that smbclient hangs when I try to access files on a particular Windows XP share. The oddest thing is that I can access other shares on the same XP machine. I also have no problems accessing shares on a windows 98 machine on the same network. Just to make it doubly weird, my SUSE 9.2 machine upstairs can access the trouble-causing Windows XP share with no problem. Here's some diagnotic output: ******** first check service ***************** kmp@ravenclaw:~> smbclient -L hp Password: Domain=[HP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- hppsc120 Printer hp psc 1200 series IPC$ IPC Remote IPC print$ Disk Printer Drivers SharedDocs Disk SHP Files Disk transfer Disk Optimise Disk Domain=[HP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- Workgroup Master --------- ------- *************** now get content of a directory **************** kmp@ravenclaw:~> smbclient //hp/SharedDocs Password: Domain=[HP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] smb: \> dir . D 0 Thu Feb 21 12:26:16 2002 .. D 0 Thu Feb 21 12:26:16 2002 desktop.ini HS 129 Sun Nov 7 12:56:48 2004 My Pictures DR 0 Thu Feb 21 12:42:30 2002 My Music DR 0 Thu Feb 21 12:42:30 2002 63883 blocks of size 65536. 2777 blocks available smb: \> kmp@ravenclaw:~> ************** no problem so far ********************** **************** now get contents of the problem share ************** kmp@ravenclaw:~> smbclient //hp/transfer Password: Domain=[HP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] smb: \> dir ************** smbclient just hangs here ********************** Nothing has changed on the Windows XP machine, so the problem must be with SUSE 9.3. My 9.3 machine still works absolutely fine as a samba server. Any ideas on this? Is this some conflict caused by upgrading from 9.0 to 9.3? Or is it some obscure firewall problem? Any help would be appreciated. Thanks - Ken