Helios networking question

Rich · 01-23-2004, 02:17 PM

Ok, here is the readers digest version of what I have going and maybe someone else has run into this. I had a 2 station LAN set up running 9.4. With Andys help I added a 3rd station also on 9.4. The first two stations were on WIN98 and the 3rd was WINME. I updated the 3rd station to WIN2000 in order to get ready to go to version 10 or 11. Now on the 3rd station I cannot get Helios to work. I can see the network, I can open Helios in demo mode and see transactions done on the server and pull up customers. When you go to open Helios it gives you an error message that says it cannot see the timer and then gives you the rest of the demo notices. I have used the multiuser set up disk to set it up the way it was before I updated to WIN2000 and I am close but it will not work. Any thoughts?

Andy · 01-25-2004, 08:21 AM

The fact that you can see the clients and transactions means that you have properly Networked and Mapped the Helios Data directory from the Server to the Workstation ... all good on that front.

Now the second step is to tell the Workstation where the Timer Server (thus Dongle is) ... on the workstation ... View ... Preferences ... System ... Site Info ... ensure the correct System Files (for the workstation) is selected ... Timer Server is set to Client ... LAN ... either the Computer Name or IP Address of the Server (in V10 and V11 must be IP Address) ... F10 save ... close Helios ... open Helios and all should be well.

So in summary two parts to this process

... Getting at you Data ... Sharing, Mapping and using MultiUser Tools in Helios to point to the Server Database.

... Using the Dongle/Timer Manager from the Server on a Workstation ... set up the Site Info properly in Helios regarding System File for the Workstation and the necessary Timer Server info within ... System Defaults/Settings.

On the issue of internal IP Address for a LAN ... make you life easy here and use a Linksys Broadband router for Networking and your Server will 99.99% be IP Address 192.168.1.100 assigned by the Router).

Rich · 01-25-2004, 10:03 AM

I have checked the settings in the system file and they are the same way they were in was working before I upgraded from WINME to WIN2000. It is set for LAN, the computer name is correct and so on. Nothing on that stage seems to have changed from before the upgrade. That is what is so frustrating to me, it all looks like it should work. Computers will one day ruin the world!

Andy · 01-25-2004, 10:21 AM

OK ... so just to be sure ... what message are you getting going into Helios on the Workstation?

Rich ... I can assure you ... Computers "on their own" will not one day ruin the world. Bill Gates would have a part in it as well as other ... lol ... love those inconsistencies between Windows Operating systems ...

Rich · 01-25-2004, 10:22 AM

It says that it cannot communicate with the timer. I wish, and I am sure you do to, that I had written it down but I didn't. I will be in the salon in the morning and do it and write it down exactly for you. Sorry to be such a pain, I know you are busy. Thanks for your help and have a good weekend.

Rich · 01-26-2004, 09:32 AM

OK Andy, here we go. The error message that I get says "Authoritative Hose Not Found". After you click through that of course you get the one saying that you do not have the correct key since it is not finding the dongle. I also get an error message that says "Helios cannot cannot establish connection with timer server. Please verify that the timer is running and that you have a valid computer name/IP address specified in the system defaults. You will have to restart Helios for the changes to take affect". I checked in the systems page and the settings are the same as on the first server. The computer name is the same and it is set to LAN. I am open to suggestions. Thanks for the help.

Sonshinetans · 01-26-2004, 11:04 AM

I had the same problem when I changed to windows 2000. I tried to leave one computer on win98 -had the same networking problem. I changed both systems to win2000 and everything is fine.
This is good news to me though, I didn't know you could network 3 computers off of one dongle. How did you setup the 3rd computer.

Rich · 01-26-2004, 12:19 PM

So it would be your best quess that changing the server to WIN2000 would take care of it then?

TikiTanningChris · 01-29-2004, 05:32 AM

Go into the utilities folder on your 9.4 disk and look for a program that sets up the LAN properties for the helios program. I had this same problem...being able to see the data through the network drive and having all the correct settings in system defaults and I found that the program in the utility folder was the answer to my problem. --Chris

Andy · 01-29-2004, 10:48 PM

Rich ... that message says that the Timer Server program in System Settings is not configured properly.

The MultiUser Setup only relates to changing the data path ... has no bearing on the Host Authentication for the Timer Server.

Make sure your using a separate System File record (on Site Info) for the Workstation apart from the Server (likely Default 0 for the Server) you need a separate record for the Workstation ... that record would be set to LAN and that it is a Client (not Server) and the IP address or Computer Name of the Server ... Save it (if you had to create a new record, you may have to reset your Client Profile Accumlator Names / User Defined Fields as well as your Equipment Bed Types ... that info is stored on the System File record so be aware thereof and check each after exiting System Settings.

Close Helios and restart ... that is the only area that will give the Host Authentication problem ... of course the LAN not working properly would also ... but if you can see your clients (f2) on the Workstation that is not a issue ... you have to get the Site Info right regarding the Timer Server and System Files.

Hope this helps ...

_________________

Andy Thompson
Authorized HELIOS Independent Consultant
877-777-6717
andy@myatso.com[ This Message was edited by: Andy @ MyATSO.ca on 2004-01-29 22:51 ]

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
HELIOS QUESTION. mdb crystal reports and access	jeradsv	Technology Forum	4	08-19-2005 03:56 PM
HELIOS Regional Trainings - Winter Schedule	Andy	Technology Forum	3	11-09-2004 07:19 PM
Finalizing before networking Helios WAN Version 10	shybabie	Technology Forum	3	02-04-2004 08:13 PM
more about Helios V10	Andy	Technology Forum	3	05-28-2002 08:35 AM
Helios Local Networking	Andy	Technology Forum	3	08-02-2001 12:55 AM

01-23-2004, 02:17 PM	#1 (permalink)
Rich Join Date: Jan 27 2000 Location: Topeka Kansas Age: 52 Posts: 484 Rep Power: 9	Ok, here is the readers digest version of what I have going and maybe someone else has run into this. I had a 2 station LAN set up running 9.4. With Andys help I added a 3rd station also on 9.4. The first two stations were on WIN98 and the 3rd was WINME. I updated the 3rd station to WIN2000 in order to get ready to go to version 10 or 11. Now on the 3rd station I cannot get Helios to work. I can see the network, I can open Helios in demo mode and see transactions done on the server and pull up customers. When you go to open Helios it gives you an error message that says it cannot see the timer and then gives you the rest of the demo notices. I have used the multiuser set up disk to set it up the way it was before I updated to WIN2000 and I am close but it will not work. Any thoughts?

01-25-2004, 08:21 AM	#2 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,760 Rep Power: 9	The fact that you can see the clients and transactions means that you have properly Networked and Mapped the Helios Data directory from the Server to the Workstation ... all good on that front. Now the second step is to tell the Workstation where the Timer Server (thus Dongle is) ... on the workstation ... View ... Preferences ... System ... Site Info ... ensure the correct System Files (for the workstation) is selected ... Timer Server is set to Client ... LAN ... either the Computer Name or IP Address of the Server (in V10 and V11 must be IP Address) ... F10 save ... close Helios ... open Helios and all should be well. So in summary two parts to this process ... Getting at you Data ... Sharing, Mapping and using MultiUser Tools in Helios to point to the Server Database. ... Using the Dongle/Timer Manager from the Server on a Workstation ... set up the Site Info properly in Helios regarding System File for the Workstation and the necessary Timer Server info within ... System Defaults/Settings. On the issue of internal IP Address for a LAN ... make you life easy here and use a Linksys Broadband router for Networking and your Server will 99.99% be IP Address 192.168.1.100 assigned by the Router).

01-25-2004, 10:03 AM	#3 (permalink)
Rich Join Date: Jan 27 2000 Location: Topeka Kansas Age: 52 Posts: 484 Rep Power: 9	I have checked the settings in the system file and they are the same way they were in was working before I upgraded from WINME to WIN2000. It is set for LAN, the computer name is correct and so on. Nothing on that stage seems to have changed from before the upgrade. That is what is so frustrating to me, it all looks like it should work. Computers will one day ruin the world!

01-25-2004, 10:21 AM	#4 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,760 Rep Power: 9	OK ... so just to be sure ... what message are you getting going into Helios on the Workstation? Rich ... I can assure you ... Computers "on their own" will not one day ruin the world. Bill Gates would have a part in it as well as other ... lol ... love those inconsistencies between Windows Operating systems ...

01-25-2004, 10:22 AM	#5 (permalink)
Rich Join Date: Jan 27 2000 Location: Topeka Kansas Age: 52 Posts: 484 Rep Power: 9	It says that it cannot communicate with the timer. I wish, and I am sure you do to, that I had written it down but I didn't. I will be in the salon in the morning and do it and write it down exactly for you. Sorry to be such a pain, I know you are busy. Thanks for your help and have a good weekend.

01-26-2004, 09:32 AM	#6 (permalink)
Rich Join Date: Jan 27 2000 Location: Topeka Kansas Age: 52 Posts: 484 Rep Power: 9	OK Andy, here we go. The error message that I get says "Authoritative Hose Not Found". After you click through that of course you get the one saying that you do not have the correct key since it is not finding the dongle. I also get an error message that says "Helios cannot cannot establish connection with timer server. Please verify that the timer is running and that you have a valid computer name/IP address specified in the system defaults. You will have to restart Helios for the changes to take affect". I checked in the systems page and the settings are the same as on the first server. The computer name is the same and it is set to LAN. I am open to suggestions. Thanks for the help.

01-26-2004, 11:04 AM	#7 (permalink)
Sonshinetans Join Date: Oct 23 2000 Location: alabama Posts: 493 Rep Power: 8	I had the same problem when I changed to windows 2000. I tried to leave one computer on win98 -had the same networking problem. I changed both systems to win2000 and everything is fine. This is good news to me though, I didn't know you could network 3 computers off of one dongle. How did you setup the 3rd computer.

01-26-2004, 12:19 PM	#8 (permalink)
Rich Join Date: Jan 27 2000 Location: Topeka Kansas Age: 52 Posts: 484 Rep Power: 9	So it would be your best quess that changing the server to WIN2000 would take care of it then?

01-29-2004, 05:32 AM	#9 (permalink)
TikiTanningChris Join Date: Mar 9 2003 Posts: 10 Rep Power: 0	Go into the utilities folder on your 9.4 disk and look for a program that sets up the LAN properties for the helios program. I had this same problem...being able to see the data through the network drive and having all the correct settings in system defaults and I found that the program in the utility folder was the answer to my problem. --Chris

01-29-2004, 10:48 PM	#10 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,760 Rep Power: 9	Rich ... that message says that the Timer Server program in System Settings is not configured properly. The MultiUser Setup only relates to changing the data path ... has no bearing on the Host Authentication for the Timer Server. Make sure your using a separate System File record (on Site Info) for the Workstation apart from the Server (likely Default 0 for the Server) you need a separate record for the Workstation ... that record would be set to LAN and that it is a Client (not Server) and the IP address or Computer Name of the Server ... Save it (if you had to create a new record, you may have to reset your Client Profile Accumlator Names / User Defined Fields as well as your Equipment Bed Types ... that info is stored on the System File record so be aware thereof and check each after exiting System Settings. Close Helios and restart ... that is the only area that will give the Host Authentication problem ... of course the LAN not working properly would also ... but if you can see your clients (f2) on the Workstation that is not a issue ... you have to get the Site Info right regarding the Timer Server and System Files. Hope this helps ... _________________ Andy Thompson Authorized HELIOS Independent Consultant 877-777-6717 andy@myatso.com[ This Message was edited by: Andy @ MyATSO.ca on 2004-01-29 22:51 ]

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)