Mombu the Programming Forum sponsored links

Go Back   Mombu the Programming Forum > Programming > error SYS0071
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 20th April 00:45
spam
External User
 
Posts: 1
Default error SYS0071



'm running a small peer to peer net (mainly os/2, a couple win98, one
linux) with one computer("ONE" running os/2 4.53) acting as a non-dedicated
server.

When trying to access "ONE", Periodically I get sys0071, here is clip of
the help for that:

SYS0071: The network request was not accepted.

EXPLANATION: One of the following occurred:
o The specified server cannot support the network request.
o The server might have run out of network resources such as memory,
network buffers, or NETBIOS commands necessary to process your
request.
o The maximum number of users for the alias may have been reached.


Other computers that have already accessed this (or other resources) on
ONE have no trouble continuing their connections.

ONE is seen in the Network "browser" folder, but on clicking on it from
the troubled computer you get the same error popup.

The computer that can't log into ONE's resources will vary.

This can occur from an ecs computer or a windoze computer (forget the
exact error in windoze, but it is similar)


STOPping and then reSTARTing "File and Print client" on ONE fixes all
this for a while, but this is not really practical as I'd have to keep
doing this periodically.

When the error occurs, there is no problem for ONE to access the
computer having trouble accessing it, so it is stricly one way.

TCPIP runs fine, can ping and so on.


eCS's default setup of NetbiosOverTCPIP (TCPBEUI), plain TCPIP & Netbios
are installed on the OS/2 machines.


Here is the peer section from IBMLAN.INI:

==================================

[peer]

auditing = resource
; The following parameters generally do not need to be
; changed by the user. NOTE : srvnets= is represented in
; the server info struct as a 16-bit lan mask. Srvnet names
; are converted to indexes within [networks] for the named nets.
guestacct = guest
autodisconnect = -1
maxauditlog = 100
maxchdevjob = 2
maxchdevs = 1
maxconnections = 26
maxlocks = 64
maxopens = 2048
maxsearches = 150
maxsessopens = 80
maxsessreqs = 25
maxsessvcs = 1
maxshares = 16
maxusers = 5
numbigbuf = 4
numfiletasks = 1
numreqbuf = 48
sizreqbuf = 4096
srvhidden = no

========================

Can anyone help? Any suggestions?


--
* Orest

~~~
Ontario, Canada


--
* Orest

~~~
Ontario, Canada
  Reply With Quote


  sponsored links


2 20th April 00:45
al savage
External User
 
Posts: 1
Default error SYS0071



At first, I thought that I knew the answer:
o Microsoft Knowledge Base Article - 323582
o Net3101 Error on OS/2 Server Because of SessionSetup SMB

The symptoms are very, very similar to what you describe. But it
doesn't appear to be a problem with W98, and the OS/2 error number is
different. Otherwise, it's a perfect fit ;O

Sadly, I do not know the true answer.

--
Regards,
Al S.
  Reply With Quote
3 20th April 00:45
william l. hartzell
External User
 
Posts: 1
Default error SYS0071


Sir:

WAG: Could you be running out of sockets? Google on these newsgroups.
There is a rexx script that will run that can close open, unused
sockets. Use a cron the run it often as necessary. I've heard that
there is a limit as the number of customers that a peer will service, to
keep it distinct from the server product. Look in the archives of these
networking newsgroups for alternatives.
--
Bill
Thanks a Million!
  Reply With Quote
4 25th April 09:56
al savage
External User
 
Posts: 1
Default error SYS0071


I thought that that script was for TCP/IP sockets, not NetBIOS sockets.

--
Regards,
Al S.
  Reply With Quote
5 25th April 09:56
william l. hartzell
External User
 
Posts: 1
Default error SYS0071


Sir:

I'd assumed that he was running tcpbeui since he mentioned Linux.
--
Bill
Thanks a Million!
  Reply With Quote
6 25th April 09:56
al savage
External User
 
Posts: 1
Default error SYS0071


He is:

"eCS's default setup of NetbiosOverTCPIP (TCPBEUI), plain TCPIP &
Netbios are installed on the OS/2 machines."

But,
"TCPIP runs fine, can ping and so on."

and

"STOPping and then reSTARTing "File and Print client" on ONE fixes all
this for a while . . . "

I'm not sure if the unclosed sockets issue would affect ping, but I'm
pretty sure that stopping and starting Peer wouldn't have any effect on
TCP/IP sockets.

--
Regards,
Al S.
  Reply With Quote
7 25th April 09:56
spam
External User
 
Posts: 1
Default error SYS0071


It may not work, but I will search for it and try it.


It begs another question. If BOTH TCPBEUI & NETBEUI are configured on two individual
machines that are talking to each other with netbios (sharing files/printer), which
protocol is used in preference?

Perhaps my question is meaningless, because of the way this works, but I'm confused about
this.

Would removing TCPBEUI where I didn't have to have it lessen SYS0071?


Also, I do have TCPBEUI installed because I have a linux machine on the net, otherwise I'd
prefer only NetBEUI as it canNOT be routed (security concerns).

Is there any reason to run TCPBEUI, unless you have to talk to Samba or maybe XP in its
default setup? I would think that a "stacked" protocol like TCPBEUI would be less
efficient then NETBEUI.


--
* Orest

~~~
Ontario, Canada
  Reply With Quote
8 25th April 09:56
al savage
External User
 
Posts: 1
Default error SYS0071


That's a good Q. Certainly, I do not know.

Not unless you need to use NetBIOS shares across a router. And TCPBEUI
is a bigger security risk (as opposed to NetBIOS).

Quite a bit less efficient. That's why M$ makes it the default now

--
Regards,
Al S.
  Reply With Quote
9 25th April 09:56
eric w
External User
 
Posts: 1
Default error SYS0071


10-15% less efficient.

I would use NETBEUI with XP (requires a bit of XP configuration) & delete
TCPBEUI unless I was FORCED to deal with SAMBA.

....eric
  Reply With Quote
10 25th April 09:56
william l. hartzell
External User
 
Posts: 1
Default error SYS0071


Sir:

Ping does not use sockets. In fact the use of sockets is not required
for any application software. Sockets interface was ported from Netbios.

The other issue of resource limits would be affected by stopping and
starting Peer, as it would close out the use of existing connections.
The autodisconnect parameter would have the effect of closing open
connections that Windows is noted for leaving open after using. I'd
suggest a google search on this parameter. Believe -1 means to do nothing.
--
Bill
Thanks a Million!
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666