S
Stuart
We recently had broadband ADSL installed at our main and satellite offices -
both are tiny LAN set-ups which would periodically dial ISDN to enable
synchronisation of a line of business database.
Now with an ADSL router at either end the goal is to use VPN to achieve
synchronisation. At the main office with one server and seven clients, the
broadband internet works brilliantly with the server plugged into the router
*if* the router is not connected to the LAN hub. As soon as I connect the
router to the LAN via another port all Internet traffic stops - the LAN
still functions perfectly and all the clients are receiving perfectly valid
TCP/IP settings from the router. I cannot fathom why plugging in the LAN
should cause the Internet link to fail.
Clients are accepting routable IPs from a small CIDR range assigned by our
ISP, though if I switch to non-routable 192.168 addresses and try to use NAT
the situation still remains the same. I have spent a lot of time verifying
cabling and TCP/IP settings, but now I'm stumped as to how to further
troubleshoot the system.
I would be grateful for any suggestions about how to pin-point the problem -
eventually the parters plan to install Terminal Services at the main office
and use our clunky old local and remote machines as thin client terminals,
however we are totally stalled in the migration process.
Thanks in advance.
Stuart
both are tiny LAN set-ups which would periodically dial ISDN to enable
synchronisation of a line of business database.
Now with an ADSL router at either end the goal is to use VPN to achieve
synchronisation. At the main office with one server and seven clients, the
broadband internet works brilliantly with the server plugged into the router
*if* the router is not connected to the LAN hub. As soon as I connect the
router to the LAN via another port all Internet traffic stops - the LAN
still functions perfectly and all the clients are receiving perfectly valid
TCP/IP settings from the router. I cannot fathom why plugging in the LAN
should cause the Internet link to fail.
Clients are accepting routable IPs from a small CIDR range assigned by our
ISP, though if I switch to non-routable 192.168 addresses and try to use NAT
the situation still remains the same. I have spent a lot of time verifying
cabling and TCP/IP settings, but now I'm stumped as to how to further
troubleshoot the system.
I would be grateful for any suggestions about how to pin-point the problem -
eventually the parters plan to install Terminal Services at the main office
and use our clunky old local and remote machines as thin client terminals,
however we are totally stalled in the migration process.
Thanks in advance.
Stuart