Networking workstation with helios - tanTALK

secretsun02 · 01-31-2003, 04:25 PM

I am trying to network my two computers so that they can both run at the same time and use the same timer system. I bought everything through helios so I don't understand why I can't get this all set up. I am already in season and am just getting swamped with only one computer being able to run. What do I need to do?

ponyr1de · 01-31-2003, 11:19 PM

We are in the same situation.... We just installed the newest version 10.0.81 on both (new) computers and cannot get them to network properly. Helios says it is a network problem, but the only networking issues we have come from within Helios. (go figure)
Both computers see each other.
Has anyone been able to successfully network the new version of Helios??
please help

Andy · 02-02-2003, 09:41 AM

ponyr1de, the MultiUserSetup.exe program provided with V10.0.70 did not work properly which it did with V9 ... perhaps that has been fixed in V10.0.81 then again perhaps not ... in either case there are ways around that problem by going directly into the Windows registry.

If you are using Windows XP there are also issues with how you set Security permissions, this can even apply to V9 users ... just had a good friend and client that experiences this problem with V9 and it honestly took MANY days, even with additional help from the good folks at Solarsoft and Danno here on TanTalk, to figure out what was happening and the solutions ... but we did it ... Helios Tech Support just kept referring to the problem as a Microsoft Windows problem which they were not prepared to help with ... lot of good that did THEIR (and my) client. How the solution was in fact in the approach to Windows Files Permissions ... BUT only because of the way Helios handles them. There is a info related to this ... remember it relates to V9 so may not be the V10 answer.

The first error the V9 User was getting was "Can not load MSJTER35.DLL" ... this was apparently due to Helios causing (and not necessarily at time of installation ... sometimes after a few days or weeks) corruption in the System Registry. Helios V9 MUST be installed on a XP Pro or Home system in Windows98 Compatibility mode to avoid this problem entirely. How I have a number of clients that have NOT encountered this problem but an increasing number are, so it may be something different about the more recent versions of Windows XP but it is still an issue related to Helios. If you do encounter it and you previously installed Helios V9 without using the Window 98 Compatiblity mode ... YOU MUST (after backing up your Helios data and any other data) COMPLETELY reformat your Hard Drive and reinstall Windows XP ... then install Helios V9 again using the Windows98 Compatibility mode (see the HOWTO guide on the Solarsoft Site in the Knowledge Base).

Remember the above applies to V9, I have not installed enough V10 systems to know if any issues related to this with V10 ... would hope and think not.

The second problem encountered with XP and Networking a Workstation on V9 relates to getting the following message on the Networked workstation ... Jet engine database being used exclusively by another user. When Helios again advised their User that it was a Microsoft issue and they would not help, the User contacted me again, we tried many things and I spoke to MANY people looking for a solution for my client, Michael Chunn remembered that Danno here on TanTalk had a similar problem ... call Danno and here is the solution to that problem ... WORKED INSTANTLY (Dan, Harry says THANK YOU!!!) ... XP initially configures Folder/File security using a simple approach ... you have to turn that OFF. On the Helios Server (not the Workstation) remove the Share on the Helios9 directory is it is already there (I also recommend removing the Mapping on the Workstation before removing the share on the server) and then in Microsoft Explorer on the Helios Server ... Tools ... Folder ... View ... last item relates to Using Simple Approach to Permissions ... TURN IT OFF (remove the tick) and Apply. Now go to the Helios9 (or 10) directory ... right click on it ... Sharing and Security ... Share as Helios9 ... going into Permissions on this same screen ... I recommend removing "Everyone" and recreating it ... Remove Everyone ... Add ... type in everyone (will change to Everyone underlined ... confirming it is valid) ... Ok ... ensure all options are ticked ... Read, Full Control etc ALLOW ALL. Back on the Workstation remap the Helios9 (10) directory from the Helios Server as F: (or G: or H: if F: not available).

Since this post is getting long and has covered a number of issues related to requirements for operating and Networking Helios on a XP system, I will post separately hereafter the simple steps to Network a Workstation.

Again to clarify the above mainly relates to Helios9 and Windows XP ... it may or may not apply to Helios10.

Hope this helps ...

_________________

Andy Thompson
ACT Business Solutions
Toll-Free 877-777-6717
andy@atso.ca
ACT Help Center [ This Message was edited by: Andy @ ATSO.ca on 2003-02-02 10:39 ]

Andy · 02-02-2003, 10:23 AM

Networking a Workstation with Helios:

First ensure that your Workstations are networked, configured and communicating with the TCP/IP network protocol ... you will need the IP address of the computer that will act as the Helios server later in this set up ... it will be something like 192.168.1.100 ... just an example

The computer selected as the Helios Server will have the Timer Manager and Helios Dongle (copy protection device) connected to it and logically the Helios Database will be in the Data directory of that computer.

On the Helios Server go to but do not open the HeliosX (were X is 9 or 10) folder, right click on it and Share this directory. Of course you will have turned on File Sharing in your Network set up prior to being able to do this. Ensure that Everyone (or appropriate users) have Full Control rights in premissions ... Everyone is logical here. If you are using XP and only seeing the text to allow all users to change your files ... you must turn off the simple approach to security (at least on V9 of Helios) see above post for info on that issue.

I strongly recommend ONLY sharing the HeliosX directory on the Helios Server NOT the entire C: drive ... this restricts access from the workstation to the operating system of the server.

OK, now that you have Shared the Helios9 or 10 directory on the Server over to the workstation. You must install Helios on the workstation entirely.

Map the HeliosX directory from the Helios Server as F: or G: or H: on the Workstation. Use the MultiUserSetup.exe (found in the Utilities directory on the Helios CD) to set the DATA Directory path. In V9 that is one selection, in V10 you need to set EACH appropriate Database path to the shared directory on the Helios Server. You may also need to set other directories (ie Pictures) if they are in use at your location. Save your Settings.

CAUTION: with V10 you MUST ensure you change ALL database paths to the "F:Data" directory. Helios have listed them separately related to the "Helios WAN" product ... sorry folks but I have to chuckle at this one, they say they have a WAN product that does everything that Salon Net from Solarsoft does ... BUT THEY CAN NOT HELP A USER NETWORK A SINGLE WORKSTATION WITHIN THE SALON ... as you said ponyr1de ... go figure!!!.

OK back to the job at hand, now that you have pointed Helios on your Workstation to the Helios Server ... when you open Helios on the Workstation you will see the Client file etc from the Server. BUT you will be in Demo Mode ... that is only half the trick, how we have to tell Helios on the Workstation were the TimerSvr program is running to interface to the Dongle and Timer Manager.

First on the Helios Server go into the System Preferences (V9) / Settings (V10) and go to the Site Info tab.

You could create a separate System File for the Server ... I suggest just renaming the 0-Default to 0-Server and using it ... Change the Multi User setting from None to LAN, set the Location and workstation setting as you desire ... if single location leave Location blank and likely leave workstation as 1 ... this primarily relates to allowing you to balance your Cash by Workstation on the Shift Report etc ... not really relevant to the actual setup of the Networked workstation. Leave the Timer Server setting as Server on the Helios Server. F10 Save and Esc

OK, now back on the Workstation ... into System Preferences V9 / Settings V10 and again to the Site Info tab ... matters not that you are in Demo Mode ... have to be, have not set the Timer Server yet.

Create a second System File record for this workstation, if you have additional workstations you will need more of these System File records ... ALL of the info in the System Preferences / Setting and your Client Profile Accumulator Names and User Defined Field Names together with your Equipment Bed Type settings are stored on these System Default/Preferences/Setting records, so after be sure all is set the same as on the Server except where you want it different, ie Thumbprint Serial Number, Printer Names etc.

Once you have created, saved and selected the System File record from the Workstation separate from the Server record, I suggest you F10 Save the System Preferences/Settings to ensure you are working on the right System File record, how:

1. Set Multi User to LAN if at NONE
2. Change Workstation and Location fields as desired
3. Set Timer Server to CLIENT
4. Change Locate Server to IP Address and enter the IP address of the server as outlined at the start of this post ... ie: 192.168.1.100 ... just an example, must be the IP Address of the computer on your network acting as the Helios Server.

F10 Save and Esc

Close and restart Helios ... NO Demo Mode message ... F2 confirm you are linked to / pointing at the Client Database on the Server ... MISSION ACCOMPLISHED ... Happy Networking.

Hope this helps ...

_________________

Andy Thompson
ACT Business Solutions
Toll-Free 877-777-6717
andy@atso.ca
ACT Help Center [ This Message was edited by: Andy @ ATSO.ca on 2003-02-02 10:38 ]

Andy · 02-02-2003, 10:43 AM

secretsun2 and ponyr1de, I hope that the above helps to resolve your problem.

If not I would be pleased to attempt to assist further, but in all fairness ... I trust you understand I would need compensation for additional time that I may dedicate to this issue on your behalf.

secretsun2 ... are you also using V10 and if yes, what version.

Please call my TollFree number below if I can be of further service on this issue.

ANYONE that has successfully networked multiple workstations with V10 within a salon ... please tell us it does work ... please

_________________

Andy Thompson
ACT Business Solutions
Toll-Free 877-777-6717
andy@atso.ca
ACT Help Center [ This Message was edited by: Andy @ ATSO.ca on 2003-02-02 10:46 ]

secretsun02 · 02-02-2003, 05:45 PM

Thanks Andy, one more thing and I think that I should be able to work through all of this. How do you get the IP Address. I figure that there is a way when running in DOS mode. I just don't know what demand to give the computer. Thanks for all the info, and I will definetly call, I want these computers to be set up and running properly.

Andy · 02-02-2003, 08:11 PM

You should find it in your Network Properties under TCP/IP properties. You need to have set the LAN up using IP addresses.

Helios can also function with just using the Name assigned to the Helios Server in your Identification setup of your Network but IP address is MUCH more reliable.

Danno · 02-02-2003, 10:32 PM

Nice work Andy; you are the best at this!!

Teresa · 02-02-2003, 11:57 PM

www.whatismyip.com

Andy · 02-03-2003, 02:42 AM

Teresa, neat little program.

It shows your EXTERNAL IP Address which may be different than your internal LAN IP Address.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
HELIOS Regional Trainings - Winter Schedule	Andy	Technology Forum	3	11-09-2004 07:19 PM
Helios networking question	Rich	Technology Forum	14	02-02-2004 09:26 PM
The Big Switch	tcn813	Technology Forum	5	08-17-2002 04:53 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-31-2003, 04:25 PM	#1 (permalink)
secretsun02 Join Date: Jan 14 2003 Posts: 25 Rep Power: 0	I am trying to network my two computers so that they can both run at the same time and use the same timer system. I bought everything through helios so I don't understand why I can't get this all set up. I am already in season and am just getting swamped with only one computer being able to run. What do I need to do?

01-31-2003, 11:19 PM	#2 (permalink)
ponyr1de Join Date: Sep 17 2002 Posts: 19 Rep Power: 0	We are in the same situation.... We just installed the newest version 10.0.81 on both (new) computers and cannot get them to network properly. Helios says it is a network problem, but the only networking issues we have come from within Helios. (go figure) Both computers see each other. Has anyone been able to successfully network the new version of Helios?? please help

02-02-2003, 10:23 AM	#4 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,768 Rep Power: 25	Networking a Workstation with Helios: First ensure that your Workstations are networked, configured and communicating with the TCP/IP network protocol ... you will need the IP address of the computer that will act as the Helios server later in this set up ... it will be something like 192.168.1.100 ... just an example The computer selected as the Helios Server will have the Timer Manager and Helios Dongle (copy protection device) connected to it and logically the Helios Database will be in the Data directory of that computer. On the Helios Server go to but do not open the HeliosX (were X is 9 or 10) folder, right click on it and Share this directory. Of course you will have turned on File Sharing in your Network set up prior to being able to do this. Ensure that Everyone (or appropriate users) have Full Control rights in premissions ... Everyone is logical here. If you are using XP and only seeing the text to allow all users to change your files ... you must turn off the simple approach to security (at least on V9 of Helios) see above post for info on that issue. I strongly recommend ONLY sharing the HeliosX directory on the Helios Server NOT the entire C: drive ... this restricts access from the workstation to the operating system of the server. OK, now that you have Shared the Helios9 or 10 directory on the Server over to the workstation. You must install Helios on the workstation entirely. Map the HeliosX directory from the Helios Server as F: or G: or H: on the Workstation. Use the MultiUserSetup.exe (found in the Utilities directory on the Helios CD) to set the DATA Directory path. In V9 that is one selection, in V10 you need to set EACH appropriate Database path to the shared directory on the Helios Server. You may also need to set other directories (ie Pictures) if they are in use at your location. Save your Settings. CAUTION: with V10 you MUST ensure you change ALL database paths to the "F:Data" directory. Helios have listed them separately related to the "Helios WAN" product ... sorry folks but I have to chuckle at this one, they say they have a WAN product that does everything that Salon Net from Solarsoft does ... BUT THEY CAN NOT HELP A USER NETWORK A SINGLE WORKSTATION WITHIN THE SALON ... as you said ponyr1de ... go figure!!!. OK back to the job at hand, now that you have pointed Helios on your Workstation to the Helios Server ... when you open Helios on the Workstation you will see the Client file etc from the Server. BUT you will be in Demo Mode ... that is only half the trick, how we have to tell Helios on the Workstation were the TimerSvr program is running to interface to the Dongle and Timer Manager. First on the Helios Server go into the System Preferences (V9) / Settings (V10) and go to the Site Info tab. You could create a separate System File for the Server ... I suggest just renaming the 0-Default to 0-Server and using it ... Change the Multi User setting from None to LAN, set the Location and workstation setting as you desire ... if single location leave Location blank and likely leave workstation as 1 ... this primarily relates to allowing you to balance your Cash by Workstation on the Shift Report etc ... not really relevant to the actual setup of the Networked workstation. Leave the Timer Server setting as Server on the Helios Server. F10 Save and Esc OK, now back on the Workstation ... into System Preferences V9 / Settings V10 and again to the Site Info tab ... matters not that you are in Demo Mode ... have to be, have not set the Timer Server yet. Create a second System File record for this workstation, if you have additional workstations you will need more of these System File records ... ALL of the info in the System Preferences / Setting and your Client Profile Accumulator Names and User Defined Field Names together with your Equipment Bed Type settings are stored on these System Default/Preferences/Setting records, so after be sure all is set the same as on the Server except where you want it different, ie Thumbprint Serial Number, Printer Names etc. Once you have created, saved and selected the System File record from the Workstation separate from the Server record, I suggest you F10 Save the System Preferences/Settings to ensure you are working on the right System File record, how: 1. Set Multi User to LAN if at NONE 2. Change Workstation and Location fields as desired 3. Set Timer Server to CLIENT 4. Change Locate Server to IP Address and enter the IP address of the server as outlined at the start of this post ... ie: 192.168.1.100 ... just an example, must be the IP Address of the computer on your network acting as the Helios Server. F10 Save and Esc Close and restart Helios ... NO Demo Mode message ... F2 confirm you are linked to / pointing at the Client Database on the Server ... MISSION ACCOMPLISHED ... Happy Networking. Hope this helps ... _________________ Andy Thompson ACT Business Solutions Toll-Free 877-777-6717 andy@atso.ca ACT Help Center [ This Message was edited by: Andy @ ATSO.ca on 2003-02-02 10:38 ]

02-02-2003, 10:43 AM	#5 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,768 Rep Power: 25	secretsun2 and ponyr1de, I hope that the above helps to resolve your problem. If not I would be pleased to attempt to assist further, but in all fairness ... I trust you understand I would need compensation for additional time that I may dedicate to this issue on your behalf. secretsun2 ... are you also using V10 and if yes, what version. Please call my TollFree number below if I can be of further service on this issue. ANYONE that has successfully networked multiple workstations with V10 within a salon ... please tell us it does work ... please _________________ Andy Thompson ACT Business Solutions Toll-Free 877-777-6717 andy@atso.ca ACT Help Center [ This Message was edited by: Andy @ ATSO.ca on 2003-02-02 10:46 ]

02-02-2003, 05:45 PM	#6 (permalink)
secretsun02 Join Date: Jan 14 2003 Posts: 25 Rep Power: 0	Thanks Andy, one more thing and I think that I should be able to work through all of this. How do you get the IP Address. I figure that there is a way when running in DOS mode. I just don't know what demand to give the computer. Thanks for all the info, and I will definetly call, I want these computers to be set up and running properly.

02-02-2003, 08:11 PM	#7 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,768 Rep Power: 25	You should find it in your Network Properties under TCP/IP properties. You need to have set the LAN up using IP addresses. Helios can also function with just using the Name assigned to the Helios Server in your Identification setup of your Network but IP address is MUCH more reliable.

02-02-2003, 10:32 PM	#8 (permalink)
Danno Join Date: Dec 10 2001 Location: Michigan Posts: 41 Rep Power: 0	Nice work Andy; you are the best at this!!

02-02-2003, 11:57 PM	#9 (permalink)
Teresa Join Date: Dec 29 2001 Location: Davenport, IA Age: 60 Posts: 2,432 Rep Power: 25	www.whatismyip.com

02-03-2003, 02:42 AM	#10 (permalink)
Andy Join Date: Jan 25 2000 Location: CT Posts: 1,768 Rep Power: 25	Teresa, neat little program. It shows your EXTERNAL IP Address which may be different than your internal LAN IP Address.

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