Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"can't find server" after 30 seconds of operation 1

Status
Not open for further replies.

360fish

IS-IT--Management
Mar 8, 2011
54
US
I am building a new aloha system - win 7 + aloha 6.7.x. Once the FOH term comes up, it works fine (I can log in, create a check, etc.) for less than a minute then it says "can't find file server"

I am under pressure to get this fixed any ideas are appreciated.

In the FOH log I find the following:

Feb 23, 12:40:25, [2564], [INFO],,"Terminal up..."
Feb 23, 12:40:25, [2564], [INFO],,"Initialization Complete. MessagePump will activate."
Feb 23, 12:40:25, [2564], [INFO],,"The Firewall is OFF."
Feb 23, 12:40:25, [2564], [INFO],,"TIMEOUTTHRESHHOLD...5.0"
Feb 23, 12:40:38, [3192], [INFO],,"IsStationOnNetwork (Station=ALOHABOH)- QueryHostStatus failed with return code 0 = NO_ERROR, and Host Status 0"
Feb 23, 12:40:38, [3192], [INFO],,"QueryHostThread() Connection to \\ALOHABOH failed"
Feb 23, 12:40:41, [2564], [INFO],,"Lost fileserver at CheckForMasterOrFileserverDown"
Feb 23, 12:40:41, [2564], [INFO],,"Enter localState[gLocalStateIndex].state SServerDown"
Feb 23, 12:40:46, [2564], [INFO],,"Enable make fileserver 1"
Feb 23, 12:40:46, [2564], [INFO],,"EnableMakeFileserver: enabled 1 automake 0"
Feb 23, 12:40:56, [3192], [INFO],,"IsStationOnNetwork (Station=ALOHABOH)- QueryHostStatus failed with return code 0 = NO_ERROR, and Host Status 0"
Feb 23, 12:40:56, [3192], [INFO],,"QueryHostThread() Connection to \\ALOHABOH failed"

During this time the z: mapping still works, a constant ping to the server shows no network interruption. lana 0 is ipv4 on both FOH and BOH. Media sense is off. FOH has full read/write to BOH. Name resolution is working fine.

any ideas?
 
Is Aloha installed on the drive under a folder bootdrv?

Also check:
1.HASP drivers need to be updated to the version supported for Windows 7 first. The HASP drivers on the current install CD will not work, options are:

a.Put the HASP key in the USB port, if using USB key, Windows 7 will update the drivers..

b.Go to and install the HASP drivers for use with Server 2008.

2.Disable IPv6 on all NIC’s.

3. User Account Control (UAC) and Data Execution Protection (DEP) should be disabled.

a.To disable User Account Control (UAC)

b. Go to start --> Control Panel --> User Account -->Change User Account Settings

- move the slider down to "Never Notify"

c. To disable Data Exection Prevention (DEP)

d. Go to start --> Accessories --> right click on command prompt --> run as Administrator

- type: bcdedit.exe /set {current} nx AlwaysOff --> enter --> reboot





Cheers,
Coorsman
 
Aloha 6.5 and above on Win7 needs to be installed as an Administrator. Also, you can try changing the environment variables to reflect the BOH IP address rather than the name.
 
Thanks for the responses.

I should have said the setup was working at some point a couple days ago. Patches, network changes, and probably drunken monkeys have been at it since, but the core build should be solid.

Coorsman - I've done all those steps (read your FAQ, plus radiant KBs) I am working on a script that automates some of those steps, plus some gpedits, I'll share it when it's in working order.

gunstar I use lmhosts files to ensure name resolution and test via other solutions, I never thought of putting the IP in the environment, it's an interesting idea but probably not causal here. Still, I'll try it to be sure.

I have a call in to radiant corporate support I'll let you know if that turns anything up but they're not The Best people, sometimes, for troubleshooting I appreciate any other thoughts all y'all have.

I have to have this fixed by tomorrow at 5 pm so...
 
Router/switch issues? Check
That a cable isn't looped back into the router.

Drunken monkeys might have found a loose patch cable and filled all the open ports. Not the first time I've had that happen.

Cheers,
Coorsman
 
@coorsman well, you got me thinking and I replaced the switch. Voila. fixed! I was using a semi-managed switch (netgear prosafe plus) and I must have had something mis-configured with ... broadcasts? Just guessing, I'll troubleshoot later.

Thanks for helping me think in the right direction.

By The Way did you see I finally responded to an old thread you asked me a question in?


So far the open mesh network equipment I talk about is awe-some
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top