Novell/Paradox ERROR notice and FIX

[Langley]

I'm posting this as a notice to all of you who use Paradox on a Novell Network with NT based workstations. We recently deployed several workstations (Win XP Pro/Paradox 9) and noticed that Paradox network applications refused to function. The standard 'Network Initialization Failed' error dialog popped up and Paradox refused to run unless we set the netfile location to the workstation (C: drive) itself - obviously NOT a solution. No matter what we changed it refused to work. We began comparing operating system builds and everything else we could think of. Finally we noticed that the Novell Client version was different on the machines which refused to run Paradox. The workstations which worked fine were using Netware Client for Windows version 4.82. The bad workstations were using version 4.83. A little investigation revealed that a new Netware patch for version 4.83 was available and that it had been written to address a similar problem with another product. The file name for the updated client on Novell's site is: WNT483e.exe (a zipped set of files). Once the patch is installed, version 4.83 works great.

Mac

"Do not delve too deeply in the arts of your enemy and so become ensnared by them"

langley_mckelvy@cd4.co.harris.tx.us

 

[footpad]

Langley,

Also, you might check to make certain that your Receive Buffer Packet Size is not set to the smallest default value. Try to boost it to something along the lines of your standard table block size; that'll help throughput tremendously.

Hope this helps...

-- Lance

 

[Langley]

Lance,

I Can't find that specific setting on this client. My netAdmin tells me that Netware handles that dynamically regardless of the setting. Mac

"Do not delve too deeply in the arts of your enemy and so become ensnared by them"

langley_mckelvy@cd4.co.harris.tx.us

 

[footpad]

Mac,

Hm. That must've changed since 3.02 of Client32. Thanks for the update. (I don't have access to a Netware environment anymore, so I'm a little out of date.)

-- Lance

 

[Guest_imported]

Watch out for Windows 2000 also as we had similar problems with that; cured by a patch from Novell