Win2K and Windows XP based POS registers canno communicate with server

[neat2006]

This is somewhat of a strange issue. Allow me to detail it as much as I can.
We use the Blackboard Transaction System (BTS) for all students dinning services. The "ENVISION" server is Running Windows 2003 Server with Oracle 8+. All clients/registers are NCR Windows-based devices with the BTS system installed. They all come pre-imaged from Blackboard. They are spread across multiple VLANs within our robust (class B) network, spread across multiple physical locations, and all use static IP addresses. Until recently, all NCR registers were Windows 98-based devices. Our problems began last year when Blackboard started shipping us Win2K-based registers. These new POS registers DO NOT or CAN NOT communicate with the ENVISION server across multiple routers or VLANs. They only work if they are attached or connected to the same local (class B) network as the server, or that network is (logically) extended to where the register is needed. If we take the same device and move it to the server network and ONLY change its IP address, it works fine. As soon as it is moved outside of that network and its IP address changed to its new local network it can no longer communicate with the server.
All windows 98-based registers work fine regardless of its location or network.
We are currently having the same issue experienced with all Win2K registers with a new shipment of Windows XP-based registers.
Here the twist: Every other TCP/IP application works fine on these new registers: Web, telnet to server over port 1312 (STI Envision), ping, tracert, map to server, etc. Only when the NEW registers try to connect to the server for the BTS system application to work is when we see a problem. Any ideas? Sorry for the LONG posting. Thanks
Nick Guareno

[Cyberdyne]

This is somewhat of a strange issue. Allow me to detail it as much as I can.
We use the Blackboard Transaction System (BTS) for all students dinning services. The "ENVISION" server is Running Windows 2003 Server with Oracle 8+. All clients/registers are NCR Windows-based devices with the BTS system installed. They all come pre-imaged from Blackboard. They are spread across multiple VLANs within our robust (class B) network, spread across multiple physical locations, and all use static IP addresses. Until recently, all NCR registers were Windows 98-based devices. Our problems began last year when Blackboard started shipping us Win2K-based registers. These new POS registers DO NOT or CAN NOT communicate with the ENVISION server across multiple routers or VLANs. They only work if they are attached or connected to the same local (class B) network as the server, or that network is (logically) extended to where the register is needed. If we take the same device and move it to the server network and ONLY change its IP address, it works fine. As soon as it is moved outside of that network and its IP address changed to its new local network it can no longer communicate with the server.
All windows 98-based registers work fine regardless of its location or network.
We are currently having the same issue experienced with all Win2K registers with a new shipment of Windows XP-based registers.
Here the twist: Every other TCP/IP application works fine on these new registers: Web, telnet to server over port 1312 (STI Envision), ping, tracert, map to server, etc. Only when the NEW registers try to connect to the server for the BTS system application to work is when we see a problem. Any ideas? Sorry for the LONG posting. Thanks
Nick Guareno

This seems to be a complex issue, I would first lay out the problem on paper or excel and find out how many routers/servers/switches the stations have to go through to communicate with the server. I would also concentrate my attention on the DNS and see if its reachable from the stations across the entire network. Also contact the manufacturer and find out what ports are used and what ports need to be opened/forwarded. So start with the basics, test connections one by one, check ports, check firewalls on the routers/switches and make sure the server is allowing connections. Also think about the fundamental differences between win98 and NT 2k/xp as far as networking is concerned. Make sure the stations are added to the domain and have proper rights for delegation with the server. Good Luck!

[neat2006]

Thanks Cyberdyne for the insight.
As far as the network is concerned, the highest number of switches/routers any one register would traverse is 2 or 3 to get to the server at any give time. All our edge switch/routers are directly linked to, and routed at our core routers. Each location having 2 links and running VRRP at the core for redundancy fail over. What is strange is that only this STI Envision BTS application (over port 1312) cannot establish, and maintain a communication with ther server, and only those running win2K and XP. As far as the basic differences between Win98 and 2K or XP, when it comes to networking interfaces properties (TTL, MTU, etc.), or protocols, I can't see how that would inpact one specific application. In addition, there are no firewalls betwen these registers and the server, except for those "client fireewalls" installed for client security. These firewalls have been configured to allow this traffic at the resgister end. The server is not running any firewalls at all. Any suggestions?
Thanks
Nick Guareno