TECHNICAL / NETWORKING: Aloha terminals losing connection to the file server - Coorsman?

[kposnet]

I have several sites where terminals will suddenly lose the file server. Here's the set up and what I have checked:

- 2 nics, WAN and LAN
- on LAN (Aloha, LANA 0), Netbios over TCP/IP is explicitly enabled in the WINS tab of the nic properties
- H-node defined in the registry
- Not using LMHOSTS, HOSTS, or DNS
- Computer Browser errors are all over the event viewer

Looking in the debout, I see sending datagram failures (no resource available) but to me, this is as a result of the problem, not the cause itself. A reboot of the file server or disabling/enabling the nic clears the cache and re-registers the terminals.

I have been able to mimic the problem by disabling the workstation service which disables the computer browser service. When in b-node, disabling this service causes immediate loss of the file server. When in h-node, the loss takes between 7 - 8 minutes after disabling the workstation service. This is because it is communicating point to point and then switches to broadcast.

Am I close to finding out why the terminals are suddenly de-registering? Am I way off? Anyone (coorsman) have any ideas?

 

[coorsman]

What windows operating systems are you using - server & terminals and what version of Aloha.

Cheers,
Coorsman

cabaretsystems.com

 

[kposnet]

Terminals are XPe and I use two images for the file server: XP Pro, SP3 and Win 7 Pro. Aloha versions are both 6.5 and 6.7, several release points trying to address this. I DO know that I started seeing this in the later versions of 6.4 but I'm almost positive that it's related to the file server image as during the 6.4 release is when the fs image began changing.

Thanks for responding, coorsman!

 

[coorsman]

Are you using AVG?

Cheers,
Coorsman

cabaretsystems.com

 

[coorsman]

Stop the browser service on all the terminals, only leave it enabled on
the FS.

sc \\term1 stop browser
sc \\term1 config browser start=disabled

From the server w/ an account that has admin rights on the terminal.



Cheers,
Coorsman

cabaretsystems.com

 

[coorsman]

Also:
If you have two NIC's make sure the internet one is set to disable netbios
over tcp/ip, not enabled or default. On the Aloha NIC make it enabled, not
default.



Cheers,
Coorsman

cabaretsystems.com

 

[kposnet]

We ARE using AVG but included all Aloha and Radiant folders in the exceptions list. Is there an issue with this av? I am having issues in other areas concerning AVG (RFS, specifically) and have been searching for a better solution. Do you know specific known conflicts?

Thanks for the tip on the browser service. I will do that in the morning and test it. Our nics are set up exactly like you described.

 

[coorsman]

Yes, I ran a search about browser errors, all pointed to 1. removing browser services on the terminals and 2. removing AVG.
Aloha suggests using MSE for virus protection.


Cheers,
Coorsman

cabaretsystems.com

 

[eburks]

I strongly recommend Microsoft Security Essentials too

It works great, it is free and stays up-to-date without a user maintaining any kind of yearly subscription or update. It is kind of like Microsoft's apology to the computer community at large for creating the monster of a security problem that is the windows operating system.

Initial install can be a little slow because the signature database update can come in a little slow due to Microsoft server congestion or slow internet but if you download the manual update file and apply it right after install but before you click any finish button or reboot; then the complete install can be done in about 5 minutes.

Manual signature update is nice to always have if you visit locations with slow internet; so I download the latest 32bit and 64bit definition file about once or twice a month and keep it on the flash drive that is always in my pocket, (the new use for that watch pocket in all my jeans)

installer and manual update here

http://windows.microsoft.com/en-US/windows/security-essentials-download

http://support.microsoft.com/kb/971606

 

[kposnet]

Just an update. I have had my suspicions about AVG and am in the process of confirming them. After attempting to MAKE it work through severely in-depth networking solutions, I have removed it from a few of our sites and installed Security Essentials. These particular sites are no longer seeing the problem. Wild and wacky, huh? Now I have to convince the powers that we should probably move away from this solution. ROI, here I come. Thanks, Coorsman, for your input!