4
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
