This client is using novell with arev. They have 5-6 stations that are working just fine but they are putting another on and they are getting

rtp27 file not openned ..

get a bunch of these until it '.. maxinum number of variables exceeded'

Environment ..

Novel NLM. Not sure of the version. Can't get into that office right now but i am sure this is a client issue.

Client: newer machine running winXP sp2

config.nt has

dos=high, umb

device=%SystemRoot%\system32\himem.sys

files=200

buffers=30

The other workstations are virtually the same. different box but basically the same settings for the novel client and the config.nt

any great ideas?

thanks

dsig

what .. no novel guys out there?

Well guessing it is losing the network connection… but why? ;)

The Sprezzatura Group

World leaders in all things RevSoft

Check frame type in network settings of client

make sure they are running the tsr

check drive mappings (and rights)

make sure EMS really is working (not just defined in the icon) by opening up an ordinary dos prompt and running MEM

this happens during startup of arev. i can continue to do things on the network and on the novel server ..

]Check frame type in network settings of client

what should it be?

]make sure they are running the tsr

they are

]check drive mappings (and rights)

appears okay .. same login works on another workstation

]make sure EMS really is working (not just defined in the icon) by opening up an ordinary dos prompt and running MEM

haven't done this but will tomorrow ..

What ever it is, is limited to this machine. Another workstation in same location works just fine. I compared all novell settings and they appeared to be all the same

thanks

dsig

Dave

The frame type should be the same as the other workstations which should be the same as is defined on the srver. The recommended is 802.2.

Also make the IPX protocol the first, if not the only, entry in the protocols list.

The Sprezzatura Group

World leaders in all things RevSoft

thanks .. i will check those also.

the thing that throws me is that i checked setting for setting between the workstation that does not work with one that does work .. they were the same

but will check again

thanks

I seem to recall this happening with Novell 6.0x with NLM and Win98 workstations. The cause was the frame type on the workstation client were set to "AUTO" instead of manually set to the same frame type as bound on the Server. The few workstations set at "AUTO" worked fine for months then one day one by one just decided to stop connecting properly (LH that is). All other Netware functions appeared fine. Nothing to my knowledge was changed on the Server. If there are several frame types defined for the client, set the type as bound on the Server to be first.

Another "gotcha" is to disable power management for the NIC. You have to dig around in the Control Panel for the NIC to find the checkbox for this something like "Allow this computer to turn off this device to save power". I've seen this cause grief to the LH NLM connection (files no longer open etc.) while not disturbing the rest of IPX traffic.

i will look at the binding .. i believe i remember them all set to auto and since all the machines were the same and xp etc i didn't think about it but will check it out. thanks

Auto seems to work until such time that Windows offends the IPX/LH gods who further refuse to communicate. Except for binding to a specific frame no other form of penance including uninstalling and reinstalling the Novell client results in absolution for "auto" binding.

Re-install Netware client.

Do not choose default. You MUST choose custom and select BOTH, IP and IPX.

Frame 802.2, protocol preference IPX.

View this thread on the Works forum...