RESOLVED - posting this so that others may learn what helped me.
It turned out to be as simple as posting 2 commands in the cisco swith that handles our router...
In Vlan 1 (the vlan with 19 terminals, the master and server) I added this to the vlan config...
IP helper-address xxx.xxx.xxx.xxx...
Hi again!
I decided to start a new thread as i am am looking at a new way to solve the previously un resolved problem...
To recap, Our aloha server and 19 terminals reside on VLAN1, we have one terminal that lives on VLAN2, and as of tonight, we have our last terminla connected to our network...
The Terminal are all running XP Pro, and the server is 2003. The terminals can all communicate with each other (both via ping IP and ping Name), and the LMHOSTS has been updated on all terminals.
St bernard's are messy to clean up after.
Zack
Yep, both of those are in order. Actually, we run this terminal for 20 days, and then bring it down the mountain and plug it into VLAN1 overnight, so that it will run another 21 days in standalone mode.
It has never worked like this (on the separate vlan) but I am tired of bringing this...
We have our Aloha server and 19 terminals in VLAN1, we have 1 terminal in VLAN2, and another terminal that we want to connect remotely via a VPN Tunnell (More on that one when we get to it.
I have enabled traffic between the two VLANs - I can ping IPS between vlans.
I updated the LMHOSTS files...
We are integrating (or trying to) Aloha and RDP. A few questions have come up that our local techs for Aloha and RDP cant answer..
1. What are the port setting for the com port between the two systems...Aloha says I need to get them from RDP, RDP says get them from aloha.
2. Local rep for Aloha...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.