My Computer Sees Netware 5.1 Server but Path Not Found in Cmd Window

[grandfatheroften]

A company I support remotely has a Netware 5.1 server that chugs along reliably year after year. It is currently used for only one old FoxPro for DOS program. Troubleshooting an error in the DOS program is hampered by a strange connection problem that has crept up on the Windows 2000 PC used.

The user's PC can navigate to the mapped volume, directory, and file, and can open files. using MyComputer (Explorer). But about 50% of the time, when the user opens a command window (Start->Run->Cmd) and then enters the mapped volume's drive letter, she gets a Network Path Not Found error.

The mapping can be restored in Windows Explorer with a reset (F5 key), but the path is still not found in the DOS emulated command window. Sometimes takes several re-boots to open and run the Novell-based application in the command window.

Any idea what could be causing this strange problem? Netware Client is 4.83sp2. Thanks for any assistance.

grandfatheroften -- now up to 14 with #15 due in Sept, '07!

 

[TheLad]

How is the server setup, I presume it is using IP? Are the IP settings on both server and workstation correct? Does a ping show 100% connectivity or do packets drop?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[grandfatheroften]

Ah, I wish it were, but it uses IPX only.

 

[marvhuffaker]

IPX is a very forgiving protocol, which means that if you have problems on your infrastructure, you might not notice it too much. The fact that you are seeing problems tells me the problem is pretty serious and that you need to identify NIC errors, Server/switch speed and duplex errors, workstation speed/duplex errors, etc.. It sounds like you are having severe packet loss, which results from network configuration problems.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[grandfatheroften]

Marvin,

You may be right; I'll certainly have the NIC and Switch checked by others--since I'm not on-site. They haven't touched the server since last fall, so I doubt that any setting on it has been changed. But someone may have messed with the switch while working on problem connecting to a shared printer on the Windows peer network.

The current problem is the entry clerk's inability to connect to Netware via the command window in order to run her FoxPro program. But I didn't mention the problem that she first encountered, namely, that FoxPro DOS will crash if she leaves the program for more than a few minutes to answer a call or to handle another task. The error message is: "[program name] has encountered an illegal instruction." followed by: "The 16-bit DOS subsystem has encountered an illegal instruction."

(Note: The program and database files are all on the Novell server)

Does this behavior of the running program suggest a more specific diagnosis.

Thanks for your assistance!

 

[marvhuffaker]

It's probably crashing like that because of the broken communication / files it needs can no longer be accessed, so it chokes. I've seen lots of apps do that. You can duplicate it by unplugging the network cable in a lot of cases.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[TheLad]

If it is as Marv suggests, I would ensure that the NetWare server is forced to a speed and duplex and that the switch matches this. Also do the same for the PC (but you can leave both the PC and it's switch connection at Auto Negotiate without the need to force either).

If you do have IP on your NetWare server, just try pinging it from the PC to see whether there are any dropped pings.

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[grandfatheroften]

Thanks Marv & TheLad for your helpful suggestions.

We haven't solved the problem yet, but with your help I have narrowed it down. My biggest problem is providing support from over 200 miles away and the fact that the only computer-savvy person there was out of town Monday morning and all day Tuesday.

Clearly your tips and all our tests indicate that the Netware connection is being lost. Also our tests indicate that: The PC's NIC & cable are fine; the switch is auto-manage & AutoNegotiate is the default; our Windows peer network is working fine so I assume the switch is fine; the Cat 5 cable from Netware server to switch is Ok; the Netware Server's NIC is onboard, so can't be swapped out to test--so could be flaky.

Downing the Dell server to reboot led to a warning that points in a new direction, however. It is an Array Manager warning. According to a Dell support site, the problem may be with the Dell/Veritas Disk Array Manager (we have disk mirroring set up).

I'm going to pursue this lead with Dell. At least we've found that re-booting the server gives the clerk enough time to complete her essential, but briefly needed DOS FoxPro task before the connection is dropped again!

 

[marvhuffaker]

Also since your Switch is Autonegotiate, make sure that the NIC on the server is set AUto also.. Should be found in INETCFG.NLM


Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LawnBoy]

I agree, fix your array issues first as that may cure the symptom.

newgrandfatheronce -- as of last Saturday

 

[grandfatheroften]

Well, the problem may be solved. Just at closing time, I asked what port on the Dell switch the cable from the DSL router was plugged in? "4" was the answer. Once I told them to plug it into port 1, (the unmarked but understood to be default WAN port) the server reconnected immediately and seems to be staying connected. We'll know more in the morning. If it hasn't solved the problem, I'll be back!

It looks like the Disk Array Manager warning was only an alert that any DAM clients would have to be re-connected after restart of the server--not an error report as I first thought.

Thanks again for your help guys!
Chuck--a happy grandfather