samba - Feb 2013 - Frustrated with "network name is no longer available"

Nothing fancy, and I've done this before...

but today I'm trying to get samba 3.10.5 with tdbsam working on Centos 6.3.

iptables is stopped on the samba server.
selinux is disabled on the samba server.
service smb and nmb are running.
samba server has an 'a' record on our dns server.
samba server is set to be a wins server.

Note- I have ANOTHER wins server on the same subnet for another samba 
server.
(the other one is production, the one i am setting up is it's replacement)

I have two windows 7 sp1 clients.
The registry settings in the samba-windows7 howto are applied to these 
machines.
both windows 7 clients are hard-coded to use our new centos 6.3 samba 
server for WINS.
both windows 7 clients were successfully joined to the domain.
One can log in as a domain user just fine.

The other gives "The specified network name is no longer available"
when
trying to log in to the domain
when logged into the problem machine as local admin, I can "net use"
the
samba server no problems.

I am thinking this means some sort of name resolution issue... but I am 
simply out of ideas.

I've gone over lots of forum and list postings, but there is simply no 
definitive answer to this issue.

!!! This shouldn't be this hard! I've done it before! What am I missing
???

here's the global section of my smb.conf
It was copied from a working configuration on another server
(workgroup and netbios names changed of course)

[global]
netbios name = city1
workgroup = city
smb ports = 139
passdb backend = tdbsam
security = user
printcap name = cups
add user script = /usr/sbin/useradd -m %u
add group script = /usr/sbin/groupadd %g
delete user script = /usr/sbin/userdel -r %u
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
logon script = logon.bat
logon drive = Z:
logon home = \\%L\%U
domain logons = Yes
os level = 35
preferred master = Yes
domain master = Yes
local master = yes
printing = cups
wins support = yes
host msdfs = yes
server signing = auto
browsable = yes
guest account = nobody
encrypt passwords = yes
domain logons = yes

On 2/1/2013 8:54 AM, Morgan Toal wrote:

OK I feel even dumber now...  I pasted the wrong text into my email due 
to my frustration level.

The error is: "there are currently no logon servers available"
as opposed to: "the network name is no longer available"

Anyway, I dumped and reloaded the problem client machine fresh with 
windows 7 again. Got the same error.

mtoal

-------- Original Message --------
Subject: 	[Samba] Frustrated with "network name is no longer
available"
Date: 	Fri, 01 Feb 2013 08:54:28 -0600
From: 	Morgan Toal <mtoal at burlingtoniowa.org>
To: 	samba at lists.samba.org



Nothing fancy, and I've done this before...

but today I'm trying to get samba 3.10.5 with tdbsam working on Centos 6.3.

iptables is stopped on the samba server.
selinux is disabled on the samba server.
service smb and nmb are running.
samba server has an 'a' record on our dns server.
samba server is set to be a wins server.

Note- I have ANOTHER wins server on the same subnet for another samba
server.
(the other one is production, the one i am setting up is it's replacement)

I have two windows 7 sp1 clients.
The registry settings in the samba-windows7 howto are applied to these
machines.
both windows 7 clients are hard-coded to use our new centos 6.3 samba
server for WINS.
both windows 7 clients were successfully joined to the domain.
One can log in as a domain user just fine.

The other gives "The specified network name is no longer available"
when
trying to log in to the domain
when logged into the problem machine as local admin, I can "net use"
the
samba server no problems.

I am thinking this means some sort of name resolution issue... but I am
simply out of ideas.

I've gone over lots of forum and list postings, but there is simply no
definitive answer to this issue.

!!! This shouldn't be this hard! I've done it before! What am I missing
???

here's the global section of my smb.conf
It was copied from a working configuration on another server
(workgroup and netbios names changed of course)

[global]
netbios name = city1
workgroup = city
smb ports = 139
passdb backend = tdbsam
security = user
printcap name = cups
add user script = /usr/sbin/useradd -m %u
add group script = /usr/sbin/groupadd %g
delete user script = /usr/sbin/userdel -r %u
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/usermod -G %g %u
add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
logon script = logon.bat
logon drive = Z:
logon home = \\%L\%U
domain logons = Yes
os level = 35
preferred master = Yes
domain master = Yes
local master = yes
printing = cups
wins support = yes
host msdfs = yes
server signing = auto
browsable = yes
guest account = nobody
encrypt passwords = yes
domain logons = yes

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

I'm not sure I've seen that message before.

Do you get it when trying to login to the domain?

or pinging it, or mounting a file system?

Have you tried looking at the traffic with "wireshark"  and seeing how
your two
clients differ in their conversation at whatever point you are failing?

Are the network and netmask settings all the same/in agreement?

Is there a name conflict between the two win7 stations?

Just some random thoughts...

You said you applied registry settings to both machines -- can you 
compare the
smb and networking sections to see if they are the same (except for the 
address?)

Are the settings on the local-security-policy page the same on both? 
(like one
doesn't have encryption turned or require ldap but not the other... or such?



Morgan Toal wrote:
>
>
> Note- I have ANOTHER wins server on the same subnet for another samba 
> server.
> (the other one is production, the one i am setting up is it's 
> replacement)
>
> I have two windows 7 sp1 clients.
> The registry settings in the samba-windows7 howto are applied to these 
> machines.
> both windows 7 clients are hard-coded to use our new centos 6.3 samba 
> server for WINS.
> both windows 7 clients were successfully joined to the domain.
> One can log in as a domain user just fine.
>
> The other gives "The specified network name is no longer
available"
> when trying to log in to the domain
> when logged into the problem machine as local admin, I can "net
use"
> the samba server no problems.
>
> I am thinking this means some sort of name resolution issue... but I 
> am simply out of ideas.
>
> I've gone over lots of forum and list postings, but there is simply no 
> definitive answer to this issue.
>
> !!! This shouldn't be this hard! I've done it before! What am I 
> missing ???
>
> here's the global section of my smb.conf
> It was copied from a working configuration on another server
> (workgroup and netbios names changed of course)
>
> [global]
> netbios name = city1
> workgroup = city
> smb ports = 139
> passdb backend = tdbsam
> security = user
> printcap name = cups
> add user script = /usr/sbin/useradd -m %u
> add group script = /usr/sbin/groupadd %g
> delete user script = /usr/sbin/userdel -r %u
> delete group script = /usr/sbin/groupdel %g
> add user to group script = /usr/sbin/usermod -G %g %u
> add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
> logon script = logon.bat
> logon drive = Z:
> logon home = \\%L\%U
> domain logons = Yes
> os level = 35
> preferred master = Yes
> domain master = Yes
> local master = yes
> printing = cups
> wins support = yes
> host msdfs = yes
> server signing = auto
> browsable = yes
> guest account = nobody
> encrypt passwords = yes
> domain logons = yes
>