Aloha over a vlan system

[coorsman]

I know this was covered a few months back but now I have a customer that had a working system and they made a change in their network. FOH terminals are looking for File server.
All permissions, file sharing and such are fine.

Debouts on terminal say determining fileserver w/no error.

The problem is they are using a different IP and subnet a real problem with Aloha, but it worked before.

The network environment 50,000 + networked computers on their lan. They have had Aloha in the café for the last 5 year. They recently made some changes to their network and it knocked out the Aloha connection.

Terminals are now looking for fileserver. Upon checking the network status, the server is 10.40.20.168 with a subnet of 255.255.254.23 The terminals are 10.40.18.67 & 68 with a subnet of 255.255.254.0

All other network variables have been resolved, permissions, sharing and such.

Other than netbios ports, is there anyone that has information on setting up a virtual network or vlan in a supersite or cisco network environment?
::
Our network for this building consists of two Cisco 6509 Core switches connected to 8 Cisco 4509 closet switches. Each floor is segmented into separate VLANS. We use 802.1q trunking and have no ACLs or firewalls on these subnets. When I run a packet trace at the file server I see the following behavior.
The FOH sends a SYN packet and the server sends a RST.

Thanks

 

[AlohaSupportTech]

Past on past experience have the customer create a VLAN on their network for the Aloha POS System. The accomplishes 2 things:
1. Isolates the "chatter" that is inherent with datagrams in Aloha to the virtual network so other critical functions that also live on the network are not affected.
2. Provide a standard IP Subnet platform for the Aloha equipment to operate. You can use the Windows Route command as needed.

 

[coorsman]

Got it working, they swore they had the netbios ports open, guess what, they weren't.