Anonymous_User Absent Member.
Absent Member.
874 views

Connection hung--cannot terminate it

Not sure this is the correct group, please redirect me if necessary--
Yesterday I had a user connection hung on a NW6.5, SP2 server from the day
before. Her connection (from a WIN XP SP2 machine with NWClient 4.9 SP2)
was holding a database and a file open, but she was shut down at the time I
got the calls about error messages on the database and the MSWord file. She
claims that her computer shut down normally without incident the night
before. To get the database back into use, I had to reboot. Familiar, or
settings that I should check? Thanks.


Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Connection hung--cannot terminate it

Hi there

Are you sure that the user in question wasn't logged in to a second
workstation that she had forgoten about? Normally a NetWare server clears
"dead" connections after maximum 60 minutes.

One way of checking that is to use the command "CLEAR STATION <connection
number>" on the server console. You can also use Monitor (or NoRM) to find
the user in question and press "Delete" to clear the connection. If the
user comes back in the connection list the Novell Client is doing a
reconnect from another workstation somewhere. Find that PC using the TCP/IP
address information in Monitor.

I assume you have a single server eDiretory tree as the reboot helped. If
you have more than one server with NDS replicas of the partition where the
user resides a reboot of the server wouldn't have helped because the client
would reconnect anyway using a replica on a different server.

Peter

> Not sure this is the correct group, please redirect me if necessary--
> Yesterday I had a user connection hung on a NW6.5, SP2 server from the day
> before. Her connection (from a WIN XP SP2 machine with NWClient 4.9 SP2)
> was holding a database and a file open, but she was shut down at the time I
> got the calls about error messages on the database and the MSWord file. She
> claims that her computer shut down normally without incident the night
> before. To get the database back into use, I had to reboot. Familiar, or
> settings that I should check? Thanks.
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Connection hung--cannot terminate it

Pat,

> Not sure this is the correct group, please redirect me if necessary--
> Yesterday I had a user connection hung on a NW6.5, SP2 server from the day
> before.


Do you have oplocks disabled? From the console do:

set client file caching enabled
set level 2 oplocks enabled

If either of them come back as "On" - turn them off with a set statement
at the beinning of the autoexec.ncf and reboot the server.


--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Connection hung--cannot terminate it

We've had good success clearing connections from Novell Remote Manager
(http://server:8008)
that wouldn't clear from the console Monitor.
Graham

"Pat Mueller" <pmueller@cmt-law.com> wrote in message
news:YGgYe.4488$Oi6.4239@prv-forum2.provo.novell.com...
> Not sure this is the correct group, please redirect me if necessary--
> Yesterday I had a user connection hung on a NW6.5, SP2 server from the day
> before. Her connection (from a WIN XP SP2 machine with NWClient 4.9 SP2)
> was holding a database and a file open, but she was shut down at the time

I
> got the calls about error messages on the database and the MSWord file.

She
> claims that her computer shut down normally without incident the night
> before. To get the database back into use, I had to reboot. Familiar, or
> settings that I should check? Thanks.
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Connection hung--cannot terminate it

Hamish,
Thanks, As of Friday, I now have the first line for file caching set to off,
but do not have the level 2 oplocks statement at all. All is fine so far
today (fingers crossed). I also updated a few straggler machines to the
latest client, 4.91. I read TID 10071902 and used that as a basis. I
believe that the hang up started with a database application here that is
not client server based. We have been running this app for years, but just
installed an updated version. I got a little confused as to whether to set
the level 2 oplocks also, you think that is necessary I gather?
"Hamish Speirs" <hamish@haitch.net> wrote in message
news:gu0903xfjr.ln2@news.haitch.net...
> Pat,
>
>> Not sure this is the correct group, please redirect me if necessary--
>> Yesterday I had a user connection hung on a NW6.5, SP2 server from the
>> day before.

>
> Do you have oplocks disabled? From the console do:
>
> set client file caching enabled
> set level 2 oplocks enabled
>
> If either of them come back as "On" - turn them off with a set statement
> at the beinning of the autoexec.ncf and reboot the server.
>
>
> --
> Hamish Speirs
> Novell Support Forums Volunteer Sysop.
>
> http://haitch.net
>
> (Please, no email unless requested. Unsolicited support emails will
> probably be ignored)



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Connection hung--cannot terminate it

Pat,

> Thanks, As of Friday, I now have the first line for file caching set to off,
> but do not have the level 2 oplocks statement at all. All is fine so far
> today (fingers crossed). I also updated a few straggler machines to the
> latest client, 4.91.


If ALL the client PC's are upto 4.91, you could try re-enabling oplocks.

> installed an updated version. I got a little confused as to whether to set
> the level 2 oplocks also, you think that is necessary I gather?


I'd turn both off - but as above, if every single workstation is uto
current client code, you can try re-enabling them.


--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.