OT: windows/linux networking problems

[spodosaurus]

Hi all,

I've recently had to do a reformat/reinstall of windows (SURPRISE!!!)
twice in the last week. Seems it's almost working right, except when I
try to browse for samba shares in Windows Explorer. The samba shares are
hosted on a fedora core 3 box running samba 3.0.10.

When I try to find the samba shares in "my network places" nothing shows
up (including the XP computer itself) and when I click on the workgroup
in Windows Explorer I get:

"Workgroup is not accessible. You might not have permission to use this
netowrk resource. Contact the administrator of this server to find out
if you have access permissions.

The network name cannot be found."

Now if I searcher for the samba server, I can find it and map the
network drives. However, if i log off and the xp box goes to standby, I
can't log back in: the system freezes on "Loading your personal
settings". Microsoft suggests that this is due to inaccessible mapped
network drives, and removing the mapping removes the problem.

I'm at a loss on how to fix these errors which are very probably
related. The samba usernames and passwords work and are the same as the
windows logon usernames and passwords.

Does anyone have any suggestions to resolve this?

TIA,

Ari

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

Hi all,

I've recently had to do a reformat/reinstall of windows

WHICH windows? 1.0, 2.0, 3.0. 3.11, win95, ... ?

(SURPRISE!!!)
twice in the last week. Seems it's almost working right, except when I
try to browse for samba shares in Windows Explorer. The samba shares are
hosted on a fedora core 3 box running samba 3.0.10.

When I try to find the samba shares in "my network places" nothing shows
up (including the XP computer itself) and when I click on the workgroup
in Windows Explorer I get:

"Workgroup is not accessible. You might not have permission to use this
netowrk resource. Contact the administrator of this server to find out
if you have access permissions.

The network name cannot be found."

Odds are it's your fedora configuration: smb conf, hosts allow/deny, and
such. Are they browsable? Who's master browser? WINS? Domain? Who's
assigning IPs?

 

[johns]

Simple. You are mixing dogs and cats. Linux Samba is
about the most unstable printing environ I have ever
"tried" to keep running. Why on earth?

johns

 

[spodosaurus]

WHICH windows? 1.0, 2.0, 3.0. 3.11, win95, ... ?

XP SP2

But I think this is another standby issue. I left it running overnight,
and when I went to log in today with no mapped drives it froze on
"Loading your personal settings" again :-(

Odds are it's your fedora configuration: smb conf, hosts allow/deny, and
such. Are they browsable?

Yes, but not under WORKGROUP...I get the above error message.

Who's master browser? WINS?

No WINS server

Domain?

No domain.

Who's
assigning IPs?

Fixed IPs


--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

Simple. You are mixing dogs and cats. Linux Samba is
about the most unstable printing environ I have ever
"tried" to keep running. Why on earth?

johns

I don't print with it currently, but did for years. These file shares on
the hardware RAID from the linux box have been running since RedHat 7 or 8.

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

XP SP2

But I think this is another standby issue. I left it running overnight,
and when I went to log in today with no mapped drives it froze on
"Loading your personal settings" again :-(



Yes, but not under WORKGROUP...I get the above error message.



No WINS server



No domain.



Fixed IPs

OOOOOOOOOOOOOOOOOOOOOOkayyyyyyyyyyyyyy

service smb stop

left it off for half an hour when I got distracted

service smb start

now everything is working like it should (all computers come up in the
workgroup, etc). Now the test is to see if I can log back in after
logging out and leaving the computer to go to standby... But that still
doesn't tell me what's going on. I wonder if this has something to do
with winbindd?? I'm not running that service, and know little about it
or the windows properties associated with it.

Ari

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

OOOOOOOOOOOOOOOOOOOOOOkayyyyyyyyyyyyyy

service smb stop

left it off for half an hour when I got distracted

service smb start

now everything is working like it should (all computers come up in the
workgroup, etc). Now the test is to see if I can log back in after
logging out and leaving the computer to go to standby... But that still
doesn't tell me what's going on. I wonder if this has something to do
with winbindd?? I'm not running that service, and know little about it
or the windows properties associated with it.

Ari

During the time after I issued the service smb stop command and before I
issued the service smb start command I ran through the windows home
networking wizard (in desperation) and simply confirmed all the settings
that were already there. I wonder if that had anything to do with it, in
a wierd Microsoft back-asswards sort of way?


--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

spodosaurus wrote:

During the time after I issued the service smb stop command and before I
issued the service smb start command I ran through the windows home
networking wizard (in desperation) and simply confirmed all the settings
that were already there. I wonder if that had anything to do with it, in
a wierd Microsoft back-asswards sort of way?

Unlikely. I think at least one problem is who browse master is.

Windows may see it now because it saw the LAN announce when samba came up
but can't find it other times because there's no browse master keeping a
browse list. And without WINS to resolve host names...

Did you setup the lmhosts file?

 

[spodosaurus]

Unlikely. I think at least one problem is who browse master is.

Windows may see it now because it saw the LAN announce when samba came
up but can't find it other times because there's no browse master
keeping a browse list. And without WINS to resolve host names...

Did you setup the lmhosts file?

nope, the lmhosts was the default. What shits me is that all this worked
flawlessly before I put the new drive in and reinstalled winxp with the
slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing) and
the damned 'cannot find network' comes up again, but I can still browse
the samba shares.

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

nope, the lmhosts was the default. What shits me is that all this worked
flawlessly before I put the new drive in and reinstalled winxp with the
slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing) and
the damned 'cannot find network' comes up again, but I can still browse
the samba shares.

I've started the WINS component of samba and winbindd. Here's my
smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/03/18 18:23:27

# Global parameters
[global]
workgroup = WORKGROUP
server string = Samba Server
interfaces = eth0, lo
bind interfaces only = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
wins support = Yes
ldap ssl = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
valid users = @shareusers
write list = @shareusers
create mask = 0660
security mask = 0770
directory mask = 0770
directory security mask = 0770
hosts allow = 127., 192.168.0.
hosts deny = 0.0.0.0/0
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
available = No

[backup]
path = /pub/samba/backup
read only = No
inherit permissions = Yes

[music]
path = /pub/samba/music
read only = No
inherit permissions = Yes

I think I'm dealing with two separate problems here. One is a windows
hibernate problem which hasn't gone away despite me unticking the
hibernate option in the windows power settings. the other is a
networking problem which is now intermittent (based on a few hours of
the problem not happening, described in previous posts).

Ari

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

nope, the lmhosts was the default. What shits me is that all this
worked flawlessly before I put the new drive in and reinstalled winxp
with the slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing) and
the damned 'cannot find network' comes up again, but I can still
browse the samba shares.

I've started the WINS component of samba and winbindd. Here's my
smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/03/18 18:23:27

# Global parameters
[global]
workgroup = WORKGROUP
server string = Samba Server
interfaces = eth0, lo
bind interfaces only = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
wins support = Yes
ldap ssl = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
valid users = @shareusers
write list = @shareusers
create mask = 0660
security mask = 0770
directory mask = 0770
directory security mask = 0770
hosts allow = 127., 192.168.0.
hosts deny = 0.0.0.0/0
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
available = No

[backup]
path = /pub/samba/backup
read only = No
inherit permissions = Yes

[music]
path = /pub/samba/music
read only = No
inherit permissions = Yes

I think I'm dealing with two separate problems here. One is a windows
hibernate problem which hasn't gone away despite me unticking the
hibernate option in the windows power settings. the other is a
networking problem which is now intermittent (based on a few hours of
the problem not happening, described in previous posts).

Ari

Is your workgroup really workgroup?

Do you have the windows user in the linux shareusers group?

And why aren't the directories set to browseable?

 

[spodosaurus]

David Maynard wrote:

spodosaurus wrote:

spodosaurus wrote:

During the time after I issued the service smb stop command and
before I issued the service smb start command I ran through the
windows home networking wizard (in desperation) and simply
confirmed all the settings that were already there. I wonder if
that had anything to do with it, in a wierd Microsoft back-asswards
sort of way?



Unlikely. I think at least one problem is who browse master is.

Windows may see it now because it saw the LAN announce when samba
came up but can't find it other times because there's no browse
master keeping a browse list. And without WINS to resolve host names...

Did you setup the lmhosts file?



nope, the lmhosts was the default. What shits me is that all this
worked flawlessly before I put the new drive in and reinstalled winxp
with the slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing) and
the damned 'cannot find network' comes up again, but I can still
browse the samba shares.

I've started the WINS component of samba and winbindd. Here's my
smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/03/18 18:23:27

# Global parameters
[global]
workgroup = WORKGROUP
server string = Samba Server
interfaces = eth0, lo
bind interfaces only = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
wins support = Yes
ldap ssl = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
valid users = @shareusers
write list = @shareusers
create mask = 0660
security mask = 0770
directory mask = 0770
directory security mask = 0770
hosts allow = 127., 192.168.0.
hosts deny = 0.0.0.0/0
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
available = No

[backup]
path = /pub/samba/backup
read only = No
inherit permissions = Yes

[music]
path = /pub/samba/music
read only = No
inherit permissions = Yes

I think I'm dealing with two separate problems here. One is a windows
hibernate problem which hasn't gone away despite me unticking the
hibernate option in the windows power settings. the other is a
networking problem which is now intermittent (based on a few hours of
the problem not happening, described in previous posts).

Ari

Is your workgroup really workgroup?

for now, until I get this all working right.

Do you have the windows user in the linux shareusers group?

yes, and I can browse the shares under my network places, but not under
workgroup (no workgroup computers are displayed, and I've listed the
error message previously).

And why aren't the directories set to browseable?

Only the homes are not set to browsable, which doesn't mean that they
are not browsable, it means they're not presented as samba shares except
to the individual home directory's owner when they access the server
(it's in the man pages).



--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

spodosaurus wrote:

David Maynard wrote:

spodosaurus wrote:

spodosaurus wrote:

During the time after I issued the service smb stop command and
before I issued the service smb start command I ran through the
windows home networking wizard (in desperation) and simply
confirmed all the settings that were already there. I wonder if
that had anything to do with it, in a wierd Microsoft
back-asswards sort of way?



Unlikely. I think at least one problem is who browse master is.

Windows may see it now because it saw the LAN announce when samba
came up but can't find it other times because there's no browse
master keeping a browse list. And without WINS to resolve host
names...

Did you setup the lmhosts file?



nope, the lmhosts was the default. What shits me is that all this
worked flawlessly before I put the new drive in and reinstalled
winxp with the slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing)
and the damned 'cannot find network' comes up again, but I can still
browse the samba shares.


I've started the WINS component of samba and winbindd. Here's my
smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/03/18 18:23:27

# Global parameters
[global]
workgroup = WORKGROUP
server string = Samba Server
interfaces = eth0, lo
bind interfaces only = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
wins support = Yes
ldap ssl = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
valid users = @shareusers
write list = @shareusers
create mask = 0660
security mask = 0770
directory mask = 0770
directory security mask = 0770
hosts allow = 127., 192.168.0.
hosts deny = 0.0.0.0/0
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
available = No

[backup]
path = /pub/samba/backup
read only = No
inherit permissions = Yes

[music]
path = /pub/samba/music
read only = No
inherit permissions = Yes

I think I'm dealing with two separate problems here. One is a windows
hibernate problem which hasn't gone away despite me unticking the
hibernate option in the windows power settings. the other is a
networking problem which is now intermittent (based on a few hours of
the problem not happening, described in previous posts).

Ari

Is your workgroup really workgroup?

for now, until I get this all working right.

Do you have the windows user in the linux shareusers group?

yes, and I can browse the shares under my network places, but not under
workgroup (no workgroup computers are displayed, and I've listed the
error message previously).

Would seem they don't think they're in the same workgroup.

Only the homes are not set to browsable, which doesn't mean that they
are not browsable, it means they're not presented as samba shares except
to the individual home directory's owner when they access the server
(it's in the man pages).

Yes, I understand, but since 'user security' seems to be one of the
networking problems...

It was just a thought.

 

[spodosaurus]

spodosaurus wrote:

spodosaurus wrote:

David Maynard wrote:

spodosaurus wrote:

spodosaurus wrote:

During the time after I issued the service smb stop command and
before I issued the service smb start command I ran through the
windows home networking wizard (in desperation) and simply
confirmed all the settings that were already there. I wonder if
that had anything to do with it, in a wierd Microsoft
back-asswards sort of way?



Unlikely. I think at least one problem is who browse master is.

Windows may see it now because it saw the LAN announce when samba
came up but can't find it other times because there's no browse
master keeping a browse list. And without WINS to resolve host
names...

Did you setup the lmhosts file?



nope, the lmhosts was the default. What shits me is that all this
worked flawlessly before I put the new drive in and reinstalled
winxp with the slipstremed SP2.

Oh, and when I went to log on this morning, the computer froze with
"Loading your personal settings" again (and alt-tab does nothing)
and the damned 'cannot find network' comes up again, but I can
still browse the samba shares.


I've started the WINS component of samba and winbindd. Here's my
smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/03/18 18:23:27

# Global parameters
[global]
workgroup = WORKGROUP
server string = Samba Server
interfaces = eth0, lo
bind interfaces only = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
wins support = Yes
ldap ssl = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
valid users = @shareusers
write list = @shareusers
create mask = 0660
security mask = 0770
directory mask = 0770
directory security mask = 0770
hosts allow = 127., 192.168.0.
hosts deny = 0.0.0.0/0
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
available = No

[backup]
path = /pub/samba/backup
read only = No
inherit permissions = Yes

[music]
path = /pub/samba/music
read only = No
inherit permissions = Yes

I think I'm dealing with two separate problems here. One is a
windows hibernate problem which hasn't gone away despite me
unticking the hibernate option in the windows power settings. the
other is a networking problem which is now intermittent (based on a
few hours of the problem not happening, described in previous posts).

Ari


Is your workgroup really workgroup?

for now, until I get this all working right.

Do you have the windows user in the linux shareusers group?

yes, and I can browse the shares under my network places, but not
under workgroup (no workgroup computers are displayed, and I've listed
the error message previously).

Would seem they don't think they're in the same workgroup.

Only the homes are not set to browsable, which doesn't mean that they
are not browsable, it means they're not presented as samba shares
except to the individual home directory's owner when they access the
server (it's in the man pages).

Yes, I understand, but since 'user security' seems to be one of the
networking problems...

It was just a thought.

I've been going through all the options, one by one, and turning them
off, restarting samba, and turning them back on. It turns out the
problem is with the "valid users" and "write list" being set to
@shareusers. Setting it to +@shareusers doesn't help, either. It seems
like windows is timing out too soon while the user is compared with the
group on the samba server (or these settings are just borked). Is there
a way to make windows take longer before popping up an error?

Ari

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

I've been going through all the options, one by one, and turning them
off, restarting samba, and turning them back on. It turns out the
problem is with the "valid users" and "write list" being set to
@shareusers. Setting it to +@shareusers doesn't help, either. It seems
like windows is timing out too soon while the user is compared with the
group on the samba server (or these settings are just borked). Is there
a way to make windows take longer before popping up an error?

Ari

If I specify the group for each individual share, rather than in the
globals, things work okay.

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

If I specify the group for each individual share, rather than in the
globals, things work okay.

Then I'd do it that way

It's almost always a Linux Samba configuration issue because the thing is
so dern complex and it'll take 'whatever' you put in, as opposed to a
tightly integrated windows wizard.