Problem with Samba after upgrade
gayn.winters at bristolsystems.com
Sun Feb 26 07:06:04 PST 2006
> [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of
> Gerard Seibert
> Sent: Sunday, February 26, 2006 2:27 AM
> To: freebsd-questions at freebsd.org
> Subject: Problem with Samba after upgrade
> I just updated to the newest version of Samba (3.0.21b,1). The old
> version was working fine, but since there were a number of
> ports that I
> had that were out dated, I simply updated them all.
> The problem is that Samba does not appear to be working
> correctly now. I
> can access the FreeBSED machine from any of the WinXP machines without
> incident. However, the reverse is not true. I have tried running the
> following command which produces this output:
> smbclient -L boss -U username%password
> timeout connecting to 22.214.171.124:445
> timeout connecting to 126.96.36.199:139
> Error connecting to 188.8.131.52 (Operation already in progress)
> Connection to boss failed
> Absolutely nothing has changed other than the updating of Samba and a
> few other ports -- mostly KDE. The WinXP machines are untouched. There
> is no new firewall involved, etc.
> I posted this on the Samba list, but did not receive any response.
> Perhaps someone here might have an idea.
Well it looks like the personal firewall on boss got turned on.
You might check your system logs on boss to see if anything has changed
behind your back. XP tends to do this if you leave it on ... Check All
Programs -> Accessories -> System Tools -> System Information -> View ->
Can your other XP machines access boss? Try Run -> \\boss from another
XP machine to check.
Can smbclient access your samba server? I.e. can it access itself? Try
smbclient //FreeBSDname/sharename to check or try smbclient -L
//FreeBSDname to check.
You can set the debug level (-d) to 1 or 2 and see what you get.
You can also reapply the port upgrade if you think there might have been
an upgrade error.
Bristol Systems Inc.
More information about the freebsd-questions