Anonymous_User Absent Member.
Absent Member.
3240 views

Client Disconnection even causes a Server fault.

On a Win XP-Client I have the problem of disconnection to the server
after a time of inactivity. Tried serveral clients, patches, another
network-card - no effect. In the XP event log is nothing abnormal. The
client is installed with IPX-only. After that I watched the server
MONITOR.NLM to see what's happening. A thing that I must not do. With
monitor opened to the connection of the XP-cleint, the client looses the
connection and the server causes a fault:
Page Fault Prozessorausnahmebedinger (Fehlercode 00000000)
OS Version: Novell Netware 4.11
Runnig Process: Monitor-Hauptmodu Process
Stack: ...
Weitere Informationen: Die CPU hat ein Problem beim Ausführen des Codes
in NWSNUT.NLM entdeckt.

Any Ideas how to protect the server or how to heal the client. I think I
should downgrade to Windows 98. All client under Win 98 works fine but
the XP-Client makes too much trouble.
Labels (1)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

Lars,

Which version of the client (4.83, 4.90, 4.91)? If the client is
version 4.90 or 4.91, go to Control Panel, Add/Remove Programs, and
remove the NMAS Client Components. Also, did you install the client
Custom, IPX-only?

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

At the moment I have installed Clnt491g but it's the same with C483SP2g.
The NMAS Client is removed. The client is installed IPX-only. Now the
server shows:

Abbruch: Page Fault Prozessorausnahmebedingung (Fehlercode 00000000)
OS Version: Novell Netware 4.11
Running Process: Montior-Hauptmodu-Process
Stack: ...
Weiter Informationen:
Die CPU hat ein Problem beim Ausführen des Codes in MONITOR.NLM entdeckt.

Are the english-Clients better?

Best regards,

Lars
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On Sat, 06 Aug 2005 16:05:24 GMT, Lars.Pfau@pfau-modelle.de wrote:

>At the moment I have installed Clnt491g but it's the same with C483SP2g.
>The NMAS Client is removed. The client is installed IPX-only. Now the
>server shows:
>
>Abbruch: Page Fault Prozessorausnahmebedingung (Fehlercode 00000000)
>OS Version: Novell Netware 4.11
>Running Process: Montior-Hauptmodu-Process
>Stack: ...
>Weiter Informationen:
>Die CPU hat ein Problem beim Ausführen des Codes in MONITOR.NLM entdeckt.
>
>Are the english-Clients better?


Let me get one of the German SysOps to look at this.

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

I tried the english client - but it's the same. An interesting point is
the network adress of the XP-Client. All Win98/Win95 and DOS-Clients get
an own networknumber as you con see on MONITOR.NLM and with the NLIST
command, but the XP-Client gets the number 1 - the same as the server
itself. Here the output of NLIST Benutzer /a/b:

Verb *Benutzername Adresse Knoten Anmeldezeit
--------------------------------------------------------------------------
1 PFAU1.Pfau [ 8072000][ 1] 6.08.05 18:16:00
3 PFAU1.Pfau [ 8072000][ 1] 7.08.05 12:16:00
4 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
5 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
7 KASSE [ 1][ E8EDEF0D] 7.08.05 13:00:00
8 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
9 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
11 *LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
12 LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00

What can I do to give the network card und XP an adress?

Best regards,

Lars
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On Sun, 07 Aug 2005 11:02:58 GMT, Lars.Pfau@pfau-modelle.de wrote:

>I tried the english client - but it's the same. An interesting point is
>the network adress of the XP-Client. All Win98/Win95 and DOS-Clients get
>an own networknumber as you con see on MONITOR.NLM and with the NLIST
>command, but the XP-Client gets the number 1 - the same as the server
>itself. Here the output of NLIST Benutzer /a/b:
>
>Verb *Benutzername Adresse Knoten Anmeldezeit
>--------------------------------------------------------------------------
> 1 PFAU1.Pfau [ 8072000][ 1] 6.08.05 18:16:00
> 3 PFAU1.Pfau [ 8072000][ 1] 7.08.05 12:16:00
> 4 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> 5 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> 7 KASSE [ 1][ E8EDEF0D] 7.08.05 13:00:00
> 8 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> 9 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> 11 *LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
> 12 LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
>
>What can I do to give the network card und XP an adress?


I haven't worked with IPX on a Windows XP computer. My understanding
is that the Node (Knoten) for a workstation is the MAC address
hardcoded on the NIC, although I know you can change the address
reported by some NICs. You need to use the setup utility for the NIC
to do that, as far as I know. Also, is the ServerID set to 1 in
autoexec.ncf. If so, try changing that.

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On 8/7/2005 Lars.Pfau@pfau-modelle.de wrote:

> I tried the english client - but it's the same. An interesting point is
> the network adress of the XP-Client. All Win98/Win95 and DOS-Clients get
> an own networknumber as you con see on MONITOR.NLM and with the NLIST
> command, but the XP-Client gets the number 1 - the same as the server
> itself. Here the output of NLIST Benutzer /a/b:
>
> Verb *Benutzername Adresse Knoten Anmeldezeit
> --------------------------------------------------------------------------
> 1 PFAU1.Pfau [ 8072000][ 1] 6.08.05 18:16:00
> 3 PFAU1.Pfau [ 8072000][ 1] 7.08.05 12:16:00
> 4 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> 5 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> 7 KASSE [ 1][ E8EDEF0D] 7.08.05 13:00:00
> 8 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> 9 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> 11 *LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
> 12 LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
>
> What can I do to give the network card und XP an adress?
>
> Best regards,


Hence your problem. Go into Local Area Connection | Properties
and select NWLINK. Make sure the internal network is set to all
zeroes and the frame type is set to 'auto'.


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

I'm probably missing something very simple. Exactly what problem does
that cause?

To me the workstation address information shown in the message looks
like a valid workstation operating at IPX address
00000001:000000000001. (i.e. The internal network address of NWLINK
on the XP workstation.) The NetWare server is at
08072000:000000000001, so it's not like we're saying they have
conflicting internal network addresses assigned.

I would be thinking more "normal" things regarding the disconnection,
such as disabling power management on the NIC. Something like that is
going to kill your connection regardless of whether NWLINK sets up the
internal network & router or not.

For what it's worth, if disabling the internal network number for
NWLINK (by setting it to zero), DISABLE automatic frame type selection
in case there is something transmitting with an alternate IPX network
address & frame type in the environment. (Having the internal router
enabled could have masked such an issue.)

I'm like Donald of not having used IPX that much of late. Whether
MONITOR.NLM abending while sitting on the details of an IPX connection
that gets disconnected is actually unique (or an issue solved in
MONITOR.NLM or NWSNUT.NLM years ago; we are talking NetWare 4.11 here)
is not something I would even be able to test on that NetWare
platform.

But my guess would be that the MONITOR.NLM behavior is an independent
issue from why the workstation is disconnecting. Does the MONITOR.NLM
crash not happen if you sit in the details of a Windows 9x machine's
IPX connection, and then cause the Windows 9x machine to abnormally
disconnect? (e.g. Disconnect the workstation cable, and then wait for
NetWare watchdogs to kick in and disconnect the station.)

"Edison Ortiz" <eortiz@nscsysop.com> wrote:

> On 8/7/2005 Lars.Pfau@pfau-modelle.de wrote:
>
> > I tried the english client - but it's the same. An interesting point is
> > the network adress of the XP-Client. All Win98/Win95 and DOS-Clients get
> > an own networknumber as you con see on MONITOR.NLM and with the NLIST
> > command, but the XP-Client gets the number 1 - the same as the server
> > itself. Here the output of NLIST Benutzer /a/b:
> >
> > Verb *Benutzername Adresse Knoten Anmeldezeit
> > --------------------------------------------------------------------------
> > 1 PFAU1.Pfau [ 8072000][ 1] 6.08.05 18:16:00
> > 3 PFAU1.Pfau [ 8072000][ 1] 7.08.05 12:16:00
> > 4 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> > 5 PSERVER [ 8072000][ 1] 6.08.05 18:16:00
> > 7 KASSE [ 1][ E8EDEF0D] 7.08.05 13:00:00
> > 8 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> > 9 Schmider.Verwaltung [ 1][ 525400E5F5F6] 7.08.05 12:54:00
> > 11 *LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
> > 12 LPfau.Verwaltung [ 1][ 1] 7.08.05 13:00:00
> >
> > What can I do to give the network card und XP an adress?
> >
> > Best regards,

>
> Hence your problem. Go into Local Area Connection | Properties
> and select NWLINK. Make sure the internal network is set to all
> zeroes and the frame type is set to 'auto'.



Alan Adams, MCNE
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

In the protocols "NWLink IPX/SPX/NetBios-kompatibles Transportprotokol"
the internal networknumber was set to 00000001. I've tried to let it
empty. That was not possible. Now I've set it to 00000000 and it's great:
The client has a normal Node-Adress (85437234C) and has hold the
connection for more than 2 hours. Thanks a lot for your help.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On 8/7/2005 Alan Adams wrote:

> Exactly what problem does
> that cause?


Having the internal IPX number populated in NWLINK ?
It can create IPX network conflicts if those numbers aren't
documented. On a client, one shouldn't enter any number
to avoid this. However, if the server is acting as a router,
an unique internal IPX number should be used.

--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On 8/7/2005 Lars.Pfau@pfau-modelle.de wrote:

> Now I've set it to 00000000 and it's great:
> The client has a normal Node-Adress (85437234C) and has hold the
> connection for more than 2 hours. Thanks a lot for your help.


Great to hear and thanks for the post back.


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

On Sun, 07 Aug 2005 15:32:40 GMT, Lars.Pfau@pfau-modelle.de wrote:

>In the protocols "NWLink IPX/SPX/NetBios-kompatibles Transportprotokol"
>the internal networknumber was set to 00000001. I've tried to let it
>empty. That was not possible. Now I've set it to 00000000 and it's great:
>The client has a normal Node-Adress (85437234C) and has hold the
>connection for more than 2 hours. Thanks a lot for your help.


A network number of zero is a reserved number that represents the
local network segment. That should work fine fpr a client on a LAN,
as you have found. I'm glad you found the solution.

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client Disconnection even causes a Server fault.

After I changed the IPX-number to zero I can't crash the MONITOR.NLM
anymore. If I disconnect the network-cable or unpower a client the status
in MONITOR.NLM changes after a while for "Normal" to "nicht angemeldet" -
that's all - no crash - no fault. The server just works like a Novell
server should do. Because I can't reproduce the crash after changing the
IPX-number I think it was the reason.

Best regards,

Lars

> I'm probably missing something very simple. Exactly what problem does
> that cause?
>

With the IPX-number 1 the client connected to server and I could open
documents and on MONITOR.NLM I could see the opened documents. After a
periode of inactivity (about 5 minutes) the connection was lost and the
monitor.nlm crashes. If the monitor.nlm did not show that connection just
the connection was lost. The client reconnected if I click on f:, but the
opened document were closed. Now the connection is hold and the server
doesn't crash. Everything is fine.

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.