We are a small business with three offices using Wingate 5.2.2 each with a LAN behind it. At each office we have a dedicated ADSL circuit for the Wingate firewall/proxy connection. 2 branch offices connect to the head office. We use TCP mapping, port redirection, etc., to great effect.
Each office's LAN is grouped as per: 192.168.1.*, 192.168.2.* and 192.168.3.*, and Client machine IP's are manually specified in TCP/IP settings. Wingate DHCP is left on 'semi-auto' (in case we connect other PC's to the LAN), however Wingate DHCP assign gateway is off.
At each office we ALSO have a separate ADSL line for a private secure connection to a viewdata type service (we are a travel agency business). This is connected by an ADSL router, which is specified in each client TCP/IP settings as the default gateway. Also, this 'Viewdata Router' is specified in Wingate, at each office, under DHCP global options as a default gateway.
We currently run a Novell Netware V5.0 server at each location for our sales system. Each client PC logs into the local Netware Server using Netware Client. We want to map through to our Head Office via Wingate and log these clients directly onto the Head Office Server Netware Server. Using Wingate TCP mapping to Netware server port 524 we have managed to connect a remote site client to H.O. Server but cannot authenticate and run the software.
We are 'self -taught' enthusiasts who cannot afford to employ expensive Novell Engineers, does anyone know where we are going wrong?
Many thanks
Rob