Dos clients using VLM.EXE 1

[ntefft]

Straight to the point :
My company is migrating from NetWare 3.12 to NetWare 6. We have a LOT of DOS client machines that connect using VLM.EXE. Now I know that vlm can be used to make logins to NDS – I would like to know if anyone has experienced problems or limitations doing this. I’m under the impression making too many bindery logins can cause a server to stop accepting further logins. While I’m not planning on using bindery services, will using VLM to connect multiple client machines have any adverse effects?
Thanks!

 

[Provogeek]

I have seen no affects in any of my installs. I have about three clients still using VLMs for old DOS clients.

I have also had 300 node networks using bindery services on a NetWare 5.1 NDS 85 network. They work just fine. Brent Schmidt CNE,Network +
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[BKtechie]

I have a DOS client performing automated tasks using VLM.exe as well. It freezes when connected to the Server while making file modifications. Are there any settings that need to be changed to accomidate VLM clients? Any help would be much appriciated (I hate dismounting a Volume every day).
BKtechie

 

[ntefft]

BKtechie - What version of NetWare are you running?
And why is it you have to dismount a volume daily??? Could you provide more detail as to what the problem is? Your message was kinda scary

 

[BKtechie]

Yeah, dismounting a volume everyday is kinda scary. We are running Novell 6.0. We have a DOS box (VLM.exe client) that runs a bunch of batch files for polling data, sending e-mail, and other automated tasks. For some reason, since we got 6, it freezes daily while files are open on the server. When I try to use monitor to kill the connection, it freezes. When I type "CLEAR STATION ...." it freezes the console. The web admin utility doesn't kill the connection either (but it doesn't freeze). The only way to unlock these files is to dismount the volume. If you do any of the above mentioned tasks, you'll have to re-boot the server (something cute I found in a TID). I guess why this is a real PIA is that the files are crucial for our reporting and are completely locked as a result of this "bug." If anyone has any info on how to fix this, it would be much appriciated.
BKtechie

 

[Lou0686]

Hi,

Check your free block on SYS. Normally a NetWare 6 server with a low free block count will freeze/hang. Does the server perform sluggishly before the hang? This is a clue to low free block. You can check this in Monitor.

Lou

 

[BKtechie]

Lou,
The free block count is over 7 million. The server itself doesn't hang, but certain processes on the server do not respond.
It seems to happen when a DBF file is opened exclusively for maintanence. The server kicks out the user and keeps the file locked. I guess NSS doesn't like dBase or vice-a-versa. Is there anything I can do to make NSS dBase friendly?
BKtechie

 

[BKtechie]

Is there a way to remove file locks from the server or as an admin? This will prevent the dreaded dismounting.
BKtechie

 

[ltromans]

Speaking of DOS clients, since we upgraded to NW6, the old #send /a=n command in the login script no longer works to block broadcast messages. Any messages lock up the PC's until you hit CTRL-Enter.

Windows based can use the client to block broadcast message, but I see no option in DOS. Anyone have a fix?

Thanks
Leslie

 

[BKtechie]

I think I fixed it.
Here's how:
SET CLIENT FILE CACHING ENABLED=OFF
Apparently, the program didn't like the setting and was bombing out with a large cache file. Hope this helps anyone with similar problems.

BKtechie

 

[ntefft]

Hm..so was this a statement you put in the net.cfg file? I guess I should concider doing that before rollout...

 

[BKtechie]

Definately. Novell has it up on their site that the caching acts funny with all kinds of programs (Excel, WordPerfect...). Its working good with my dBase apps, no more index file recovery. Good luck with your rollout,
BKtechie