UNC path limitation

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
rjvega
Posts: 1
Joined: Wed Mar 14, 2007 2:51 pm

UNC path limitation

Post by rjvega »

I am trying to test if Hostmonitor can handle the load of our enviornment before we buy it. What I am doing is testing for 20% free diskspace on 3 volumes on 400 Novell servers (400x3 =1200 UNC tests). Some tests come back ok or bad but some others cone come back "unknown". I have the refresh set to 6 hours. Even if I go back after they time out , the test still will not work.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

That's Novell client problem. Try to set "UNC test mode" to OneByOne or OnePerServer (option located on Misc page in the Options dialog). Usually it helps.
Another possible workaround - use SNMP Get test method instead. E.g. you may check .iso.org.dod.internet.private.enterprises.novell.mibDoc.nwServer.nwFileSystem.nwFSVolTable.nwFSVolEntry.nwVolFree counter

Regards
Alex
Dubolomov
Posts: 214
Joined: Thu Jun 01, 2006 10:27 am
Location: Russia

Re: UNC path limitation

Post by Dubolomov »

rjvega wrote:I am trying to test if Hostmonitor can handle the load of our enviornment before we buy it. What I am doing is testing for 20% free diskspace on 3 volumes on 400 Novell servers (400x3 =1200 UNC tests). Some tests come back ok or bad but some others cone come back "unknown". I have the refresh set to 6 hours. Even if I go back after they time out , the test still will not work.
I had this problem. It was solved by tuning novell client options where HM (or RMA) is installed. In "Novell Client Properties" select "Additional parameters":
"Bad address cache timeout" set to "0"
"Bad server name cache enabled" set to "off"
"Bad server name cache timeout" set to "0".
After this UNC check of Novell Servers (ex. \\NW-FS1\SYS\) works fine.
Post Reply