delpheye
2010-Jun-22 11:45 UTC
[Samba] xp clients can't auth after reboot without smb restart
I currently have several fresh installs of XP that will connect to shares, but will not reconnect after a workstation reboot. These are workstations that are not joined to the domain. Only accessing shares from a local profile, but using the same user/pass to login as to connect to Samba. I get various errors at that point. Upon reboot, attempting to access the share generates: "An error occurred while reconnecting Z: to \\domain-fs\business Microsoft Windows Network: The specified network name is no longer available This connection has not been restored." At which point, attempting to re-map the drive results in an authentication window, but no correct user/pass is accepted. If I restart Samba, then the share is mapped using the workstations login credentials. Logging is set to 3 now, but I'm not even sure where to look. For some reason, restarting the daemon allows authentication to pass from clientA to Samba, but clientB is able to access the share at the same time(and vice versa after clientB has been rebooted.) My smb.conf is here: http://pastebin.ca/1888385 What could be causing this behavior? Thanks, M
Gaiseric Vandal
2010-Jun-22 17:44 UTC
[Samba] xp clients can't auth after reboot without smb restart
Which samba version? Are these XP Pro or XP Home machines. If XP Pro, have you tried joining the machine to the domain? When you map a drive letter to a samba share from XP, are you using "LocalPC\yourname" or "Domain\Yourname" when specifying credentials? Are you mapping the drive with Windows explorer or the "net" command? On 06/22/2010 07:45 AM, delpheye wrote:> I currently have several fresh installs of XP that will connect to shares, > but will not reconnect after a workstation reboot. These are workstations > that are not joined to the domain. Only accessing shares from a local > profile, but using the same user/pass to login as to connect to Samba. I > get various errors at that point. > > Upon reboot, attempting to access the share generates: > > "An error occurred while reconnecting Z: to \\domain-fs\business > Microsoft Windows Network: The specified network name is no longer available > This connection has not been restored." > > At which point, attempting to re-map the drive results in an authentication > window, but no correct user/pass is accepted. If I restart Samba, then the > share is mapped using the workstations login credentials. > > Logging is set to 3 now, but I'm not even sure where to look. For some > reason, restarting the daemon allows authentication to pass from clientA to > Samba, but clientB is able to access the share at the same time(and vice > versa after clientB has been rebooted.) > > > My smb.conf is here: http://pastebin.ca/1888385 > > What could be causing this behavior? > > Thanks, > M >
John Drescher
2010-Jun-22 17:55 UTC
[Samba] xp clients can't auth after reboot without smb restart
> "An error occurred while reconnecting Z: to \\domain-fs\business > Microsoft Windows Network: The specified network name is no longer available > This connection has not been restored." >Looks like a browsing problem to me. Try to reconnect using ip address instead of name. John
Gaiseric Vandal
2010-Jun-22 20:38 UTC
[Samba] xp clients can't auth after reboot without smb restart
in smb.conf
wins support = Yes
Don't set
wins server = ....
I don't think the nsswitch.conf is an issue- it seems like the client
has trouble finding the server. Are you using dhcp? If so, the DHCP
server (even a unix one) should be able to assign WINS. If you are not
using dhcp, or if your dhcp server can not assign wins, you can
statically set it on the XP client.
On 06/22/2010 04:24 PM, delpheye wrote:>
>
> On Tue, Jun 22, 2010 at 1:07 PM, Gaiseric Vandal
> <gaiseric.vandal at gmail.com <mailto:gaiseric.vandal at
gmail.com>> wrote:
>
> On 06/22/2010 01:55 PM, John Drescher wrote:
>
> "An error occurred while reconnecting Z: to
> \\domain-fs\business
> Microsoft Windows Network: The specified network name is
> no longer available
> This connection has not been restored."
>
>
> Looks like a browsing problem to me. Try to reconnect using ip
> address
> instead of name.
>
> John
>
>
> Are you using WINS? I find that makes a lot of issues go away.
>
>
> I have wins support enabled in Samba and the following lines in
> nsswitch.conf:
>
> debug 1
>
> passwd: files ldap
> shadow: files ldap
> group: files ldap
> hosts: files wins dns
> bootparams: files
> ethers: files
> netmasks: files
> networks: files
> protocols: files
> rpc: files
> services: files
> netgroup: files ldap
> publickey: files
> automount: files ldap
> aliases: files
>
> Is that all there is to enabling WINS?
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
>
Gaiseric Vandal
2010-Jun-22 21:01 UTC
[Samba] xp clients can't auth after reboot without smb restart
The "the semaphore timeout has expired" seems pretty significant. I bet it is related to the problem you have with your non-domain machines. I would google it. In fact I did- one post mentioned wins. Another post mentioned digital signing - which should NOT be an issue with XP and current Samba versions. On 06/22/2010 04:21 PM, delpheye wrote:> My apologies for not including this information previously. I'm > running CentOS 5.5 on Samba 3.3.8-0.52 and the machines are all XP > Pro. Joining the machine to the domain is successful sporadically, > but once the machine is joined, upon reboot and profile loading, it > returns "the semaphore timeout has expired" and loads a temporary > local profile. > > I'm mapping the drives from My Computer and when it's working, > credentials don't have to be specified because they're the same as the > user's desktop login. However, when it fails and I'm prompted for > login info, specifying domain\username or just username produces the > same results. According to samba and ldap logs, these credentials are > never passed to the server at that time. > > On Tue, Jun 22, 2010 at 12:44 PM, Gaiseric Vandal > <gaiseric.vandal at gmail.com <mailto:gaiseric.vandal at gmail.com>> wrote: > > Which samba version? > > Are these XP Pro or XP Home machines. If XP Pro, have you tried > joining the machine to the domain? > > When you map a drive letter to a samba share from XP, are you > using "LocalPC\yourname" or "Domain\Yourname" when specifying > credentials? > > Are you mapping the drive with Windows explorer or the "net" command? > > > > > > On 06/22/2010 07:45 AM, delpheye wrote: > > I currently have several fresh installs of XP that will > connect to shares, > but will not reconnect after a workstation reboot. These are > workstations > that are not joined to the domain. Only accessing shares from > a local > profile, but using the same user/pass to login as to connect > to Samba. I > get various errors at that point. > > Upon reboot, attempting to access the share generates: > > "An error occurred while reconnecting Z: to \\domain-fs\business > Microsoft Windows Network: The specified network name is no > longer available > This connection has not been restored." > > At which point, attempting to re-map the drive results in an > authentication > window, but no correct user/pass is accepted. If I restart > Samba, then the > share is mapped using the workstations login credentials. > > Logging is set to 3 now, but I'm not even sure where to look. > For some > reason, restarting the daemon allows authentication to pass > from clientA to > Samba, but clientB is able to access the share at the same > time(and vice > versa after clientB has been rebooted.) > > > My smb.conf is here: http://pastebin.ca/1888385 > > What could be causing this behavior? > > Thanks, > M > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >
John Drescher
2010-Jun-23 14:50 UTC
[Samba] Fwd: xp clients can't auth after reboot without smb restart
---------- Forwarded message ---------- From: delpheye <delpheye at gmail.com> Date: Wed, Jun 23, 2010 at 10:45 AM Subject: Re: [Samba] xp clients can't auth after reboot without smb restart To: John Drescher <drescherjm at gmail.com> On Tue, Jun 22, 2010 at 4:38 PM, John Drescher <drescherjm at gmail.com> wrote:> > On Tue, Jun 22, 2010 at 4:38 PM, Gaiseric Vandal > <gaiseric.vandal at gmail.com> wrote: > > in smb.conf > > > > ? ? ? ?wins support = Yes > > > > Don't set > > ? ? ? ? ? ?wins server = .... > > > > > > I don't think the nsswitch.conf is an issue- ?it seems like the client has > > trouble finding the server. ?Are you using dhcp? ?If so, the DHCP server > > (even a unix one) should be able to assign WINS. ? If you are not using > > dhcp, or if your dhcp server can not assign wins, you can statically set it > > on the XP client. > > > > Is the WINS server setup in the XP client?I manually specified the WINS server in the network adapater and retested, but there wasn't any change in behavior.
tms3 at tms3.com
2010-Jun-23 18:04 UTC
[Samba] xp clients can't auth after reboot without smb restart
> > --- Original message --- > Subject: Re: [Samba] xp clients can't auth after reboot without smb > restart > From: delpheye <delpheye at gmail.com> > To: Samba <samba at lists.samba.org> > Date: Wednesday, 23/06/2010 10:37 AM > > On Tue, Jun 22, 2010 at 3:38 PM, Gaiseric Vandal > <gaiseric.vandal at gmail.com>wrote: > >> >> in smb.conf >> >> wins support = Yes >> >> Don't set >> wins server = .... >> >> >> I don't think the nsswitch.conf is an issue- it seems like the client >> has >> trouble finding the server. Are you using dhcp? If so, the DHCP >> server >> (even a unix one) should be able to assign WINS. If you are not >> using >> dhcp, or if your dhcp server can not assign wins, you can statically >> set it >> on the XP client. >> >> wins server is not specified in smb.conf. I'm using DHCP but have >> never > specified a wins server in the config. I added it explicitly to one > client > and retesting resulting in no change to the issue. > > However, I noticed that wbinfo -u|g doesn't return anything, and that > seems > symptomatic of the problem at the very least. I have not determined > why > winbind doesn't work correctly, there isn't anything in my config that > suggests it's broken, yes?Winbindd isn't the issue for this. Run some nbtstats on the XP boxes: command prompt: nbstat -n nbstat -r nbstat -c After a reboot, and connect failure, do so. Then try nbstat -RR and try net drive connections. Very peculiar problem you're having.> > > > Matt > >> >> >> >> >> On 06/22/2010 04:24 PM, delpheye wrote: >> >> >>> >>> >>> On Tue, Jun 22, 2010 at 1:07 PM, Gaiseric Vandal < >>> gaiseric.vandal at gmail.com <mailto:gaiseric.vandal at gmail.com>> wrote: >>> >>> On 06/22/2010 01:55 PM, John Drescher wrote: >>> >>> "An error occurred while reconnecting Z: to >>> \\domain-fs\business >>> Microsoft Windows Network: The specified >>> network name is >>> no longer available >>> This connection has not been restored." >>> >>> >>> Looks like a browsing problem to me. Try to reconnect >>> using ip >>> address >>> instead of name. >>> >>> John >>> >>> >>> Are you using WINS? I find that makes a lot of issues go away. >>> >>> >>> I have wins support enabled in Samba and the following lines in >>> nsswitch.conf: >>> >>> debug 1 >>> >>> passwd: files ldap >>> shadow: files ldap >>> group: files ldap >>> hosts: files wins dns >>> bootparams: files >>> ethers: files >>> netmasks: files >>> networks: files >>> protocols: files >>> rpc: files >>> services: files >>> netgroup: files ldap >>> publickey: files >>> automount: files ldap >>> aliases: files >>> >>> Is that all there is to enabling WINS? >>> >>> -- To unsubscribe from this list go to the following URL >>> and read >>> the >>> instructions: https://lists.samba.org/mailman/options/samba >>> >>> >>> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> >> -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
tms3 at tms3.com
2010-Jun-23 22:57 UTC
[Samba] xp clients can't auth after reboot without smb restart
SNIP> > > > NetBIOS Names Resolved By Broadcast > ------------------------------------------ > DOMAIN.COM <1C> > DOMAIN-FS > DOMAIN.COM <1C> > DOMAIN.COM <1C> > DOMAIN-FS > DOMAIN.COM <1C> >DOMAIN.COM is a bad netbios name. I suggest something with 8 letters or numbers. Samba 3.x does not use FQDN's.> > > > nbtstat -RR: > > The NetBIOS names registered by this computer have been refreshed. > > net use y: \\domain-fs\business > Enter the user name for 'domain-fs': username > Enter the password for domain-fs: xxxxxx > System error 64 has occurred. > > The specified network name is no longer available. >>> >> >> >> >>> >>> >>> >>> Matt >>> >>>> >>>> >>>> >>>> >>>> On 06/22/2010 04:24 PM, delpheye wrote: >>>> >>>> >>>>> >>>>> >>>>> On Tue, Jun 22, 2010 at 1:07 PM, Gaiseric Vandal < >>>>> gaiseric.vandal at gmail.com <mailto:gaiseric.vandal at gmail.com>> wrote: >>>>> >>>>> On 06/22/2010 01:55 PM, John Drescher wrote: >>>>> >>>>> "An error occurred while reconnecting Z: to >>>>> \\domain-fs\business >>>>> Microsoft Windows Network: The specified >>>>> network name is >>>>> no longer available >>>>> This connection has not been restored." >>>>> >>>>> >>>>> Looks like a browsing problem to me. Try to reconnect >>>>> using ip >>>>> address >>>>> instead of name. >>>>> >>>>> John >>>>> >>>>> >>>>> Are you using WINS? I find that makes a lot of issues go away. >>>>> >>>>> >>>>> I have wins support enabled in Samba and the following lines in >>>>> nsswitch.conf: >>>>> >>>>> debug 1 >>>>> >>>>> passwd: files ldap >>>>> shadow: files ldap >>>>> group: files ldap >>>>> hosts: files wins dns >>>>> bootparams: files >>>>> ethers: files >>>>> netmasks: files >>>>> networks: files >>>>> protocols: files >>>>> rpc: files >>>>> services: files >>>>> netgroup: files ldap >>>>> publickey: files >>>>> automount: files ldap >>>>> aliases: files >>>>> >>>>> Is that all there is to enabling WINS? >>>>> >>>>> -- To unsubscribe from this list go to the following URL >>>>> and read >>>>> the >>>>> instructions: https://lists.samba.org/mailman/options/samba >>>>> >>>>> >>>>> >>>> -- >>>> To unsubscribe from this list go to the following URL and read the >>>> instructions: https://lists.samba.org/mailman/options/samba >>>> >>>> -- >>> >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >> >