Samba & Windows Error "Network Busy"

QNX Newsgroups (Archives) qdn.public.qnx4
1

Hi,

I am currently running Samba 2.0.7 on QNX 4.25 and running into an access
problem
for my Samba shares. I have several different winX machines trying to
access
my QNX box and Samba is setup to share the users folder. I have been able
to get
access to the share from network neighborhood and even map a local drive
letter
to the share. But, most of the time when I initially try to access the
share (after
rebooting WinX) I get a ‘Network Busy’ error dialog from windows and the
following
in my log.smb file:

[2001/01/30 10:42:55, 0] lib/util_sock.c:(540)
write_socket_data: write failure. Error = Broken pipe
[2001/01/30 10:42:55, 0] lib/util_sock.c:(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2001/01/30 10:42:55, 0] lib/util_sock.c:(754)
Error writing 4 bytes to client. -1. Exiting

This keeps repeating until it eventually works. Sometimes it works after a
few minutes
and sometimes it takes a few hours. It is a rather annoying intermittant
problem.

I have run thru the diagnosis.txt and the other docs in the Samba folder but
no luck
with this problem.

Here is my smb.conf:

[global]
workgroup = MIL-DOMAIN1
server string = IP # 006 : QNX Server #1
security = user
encrypt passwords = yes
guest account = guest
wins server = 192.168.0.1
local master = no
os level = 1
domain master = no
preferred master = no
hosts allow = 192.168.0. 127.
interfaces = en1

[homes]
comment = Home Directories
browseable = no
writable = yes

[Network In]
path = /NetworkIn
comment = Shared Input Folder
writeable = yes

[Network Out]
path = /NetworkOut
comment = Shared Output Folder
writeable = no

I have also run into delays waiting for ftp to open sessions but after
logging in it will ls and browse fine but when transfering (i.e. opening
a new thread and connection) it takes several seconds to start. Ping
and telenet work fine along with phindows.

Thanks…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
2

I’m not a samba expert (although I ported it), but my first guess would
be that after rebooting, the “old session” is still present on the samba
server (QNX). Assuming that is the case, you can use SWAT to manage
sessions (i.e. kill sessions) or you can kill the lingering smbd by hand
on the server. (Make sure you kill the right smbd: there’s a parent that
forks off a child for each session.)

As for the ftp problem: it could be related, or it could be a name
resolving problem: when you ftp to a machine that resolves names from a
machine that isn’t resolved, the server wants to reverse-lookup the
clients IP address, but times out because it doesn’t exist. You could
solve this by adding a fake name for your clients machine in the
/etc/hosts from your server machine, and specify the search order in
/etc/resolv.conf to look for names in /etc/hosts first:

/etc/hosts:

<your client’s IP address> fake.name


/etc/resolv.conf:

domain
nameserver <your nameserver’s IP address>
lookup file bind

Again, it could be another problem, though. The symptoms you described
doesn’t quite match the one I had. (Mine was a long delay before I got
the user prompt, but once I logged in, file transfer was normal…)

good luck,

rick

“Lee R. Copp” wrote:

Hi,

I am currently running Samba 2.0.7 on QNX 4.25 and running into an access
problem
for my Samba shares. I have several different winX machines trying to
access
my QNX box and Samba is setup to share the users folder. I have been able
to get
access to the share from network neighborhood and even map a local drive
letter
to the share. But, most of the time when I initially try to access the
share (after
rebooting WinX) I get a ‘Network Busy’ error dialog from windows and the
following
in my log.smb file:

[2001/01/30 10:42:55, 0] lib/util_sock.c:(540)
write_socket_data: write failure. Error = Broken pipe
[2001/01/30 10:42:55, 0] lib/util_sock.c:(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2001/01/30 10:42:55, 0] lib/util_sock.c:(754)
Error writing 4 bytes to client. -1. Exiting

This keeps repeating until it eventually works. Sometimes it works after a
few minutes
and sometimes it takes a few hours. It is a rather annoying intermittant
problem.

I have run thru the diagnosis.txt and the other docs in the Samba folder but
no luck
with this problem.

Here is my smb.conf:

[global]
workgroup = MIL-DOMAIN1
server string = IP # 006 : QNX Server #1
security = user
encrypt passwords = yes
guest account = guest
wins server = 192.168.0.1
local master = no
os level = 1
domain master = no
preferred master = no
hosts allow = 192.168.0. 127.
interfaces = en1

[homes]
comment = Home Directories
browseable = no
writable = yes

[Network In]
path = /NetworkIn
comment = Shared Input Folder
writeable = yes

[Network Out]
path = /NetworkOut
comment = Shared Output Folder
writeable = no

I have also run into delays waiting for ftp to open sessions but after
logging in it will ls and browse fine but when transfering (i.e. opening
a new thread and connection) it takes several seconds to start. Ping
and telenet work fine along with phindows.

Thanks…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ > http://www.michiganscientific.com
~ mailto:> <Lee.R.Copp@MichiganScientific.com>
3

“Rick Lake” <rwlake@SPAM.REDIRECTED.TO.DEV.NULL> wrote in message
news:3A7721DB.8474E94F@SPAM.REDIRECTED.TO.DEV.NULL…

I’m not a samba expert (although I ported it), but my first guess would
be that after rebooting, the “old session” is still present on the samba
server (QNX). Assuming that is the case, you can use SWAT to manage
sessions (i.e. kill sessions) or you can kill the lingering smbd by hand
on the server. (Make sure you kill the right smbd: there’s a parent that
forks off a child for each session.)

I was watching it through phindows and sin and saw the new smbd startup when
I
double clicked on the share and it just sits there for 5 or 10 seconds
before
coming up with the ‘Network Busy’…Even hand ‘killing’ the new and trying
again didn’t do the trick.

/etc/hosts from your server machine, and specify the search order in
/etc/resolv.conf to look for names in /etc/hosts first:

/etc/hosts:

your client’s IP address> fake.name


/etc/resolv.conf:

domain <your domain
nameserver <your nameserver’s IP address
lookup file bind

I’ll give this a try…

Again, it could be another problem, though. The symptoms you described
doesn’t quite match the one I had. (Mine was a long delay before I got
the user prompt, but once I logged in, file transfer was normal…)

That is roughly what I get…my ftp client says ‘connecting’ and it just
sits for
a while and then I get the ls of the default dir. File transfer speed is
decent
but each new thread/connection for each file had the same startup delay.
Annoying but not fatal…:slight_smile:

good luck,

Thanks…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
4

Lee R. Copp wrote in message <95cb5i$8lb$1@inn.qnx.com>…

You wouldn’t know about:

[2001/02/01 11:44:30, 1] lib/replace.c:(160)
WARNING: running without setgroups

would you?? It is the only thing left in my log.smb file which I’m trying
to get rid
of…The only other entries are connections and disconnects…

setgroups isn’t supported in QNX4.

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ > http://www.michiganscientific.com
~ mailto:> <Lee.R.Copp@MichiganScientific.com>
5

/etc/resolv.conf:

domain <your domain
nameserver <your nameserver’s IP address
lookup file bind

I’ll give this a try…

That did the trick. It is working very smoothly now. My Samba and FTP are
both
logging on quick and no problems. Thanks…:slight_smile:

You wouldn’t know about:

[2001/02/01 11:44:30, 1] lib/replace.c:(160)
WARNING: running without setgroups

would you?? It is the only thing left in my log.smb file which I’m trying
to get rid
of…The only other entries are connections and disconnects…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
6

“Lee R. Copp” wrote:

/etc/resolv.conf:

domain <your domain
nameserver <your nameserver’s IP address
lookup file bind

I’ll give this a try…

That did the trick. It is working very smoothly now. My Samba and FTP are
both
logging on quick and no problems. Thanks…> :slight_smile:

excellent.

You wouldn’t know about:

[2001/02/01 11:44:30, 1] lib/replace.c:(160)
WARNING: running without setgroups

I think you can just ignore this. (Or perhaps in the thousands of config
options there might be one which addresses it.) As Jay pointed out,
setgroups isn’t supported in QNX4.

would you?? It is the only thing left in my log.smb file which I’m trying
to get rid
of…The only other entries are connections and disconnects…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ > http://www.michiganscientific.com
~ mailto:> <Lee.R.Copp@MichiganScientific.com>
7

I think you can just ignore this. (Or perhaps in the thousands of config
options there might be one which addresses it.) As Jay pointed out,
setgroups isn’t supported in QNX4.

I’ll check the compile options but since it is only a warning there are
plenty of other things to do…:slight_smile:

Thanks again.

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>