Windows Forum

Ask something
Discussion Locked

T1 & DSL connections

0 helpful
5 replies

by matthew hansel

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a customer with both a point to point T1 line which is working well between their two offices. They have now added DSL to both locations. The location with the local connection to the server (the "A" side of the T1 circuit) is working great with both the T1 and the DSL - because I don't have to route the workstations through the T1 and the server is just receiving database requests from the remote side (the "Z" side of the circuit).

Now, at the "Z" end (remote office), they have the T1 router and the DSL router. I have put in two network cards in each PC that requires (1) access to the office network via T1 and (2) access to the Internet via DSL. Each card has its own IP address, subnet, gateway and DNS entries. The issue Iam having is that I can connect to the server and see the server for drive mappings and connect to the database, but not to the Internet. Or, I can connect to the Internet, but not to the database - but I can still see the server for drive mappings- I know, wierd, huh? They are using an application that runs on the Sybase SQL Anywhere database engine (version 5) - and I have tried their suggestions (setting the client to point to the "host" IP and setting the "MYIP" paramater) to no avail.
So, I am calling on you guys to help me out!

Thanks in advance!

Matthew Hansel

5 replies

by rorycarlin

It sounds like you need to set up static routes on each of your workstations using the route.exe command.

Type route /? at a command prompt to get the syntax.

What you'll need to do is configure each destination subnet to use a suitable gateway.

For example:
A workstation has two NIC with an IP address each. NIC A is 10.63.50.3 and NIC B is 10.64.50.4. NIC A is connected to LAN A which contains the Internet gateway (but on a different subnet 10.63.51.0,) and NIC B is connected to LANB which contains the office file server (but on a different subnet 10.64.51.0). LAN A's default gateway is 10.63.50.1 and LAN B's default gateway is 10.64.50.1. Still with me?

In order to communicate correctly with both the office file server and the Internet gateway, the workstation needs the following route commands entered:

ROUTE ADD 10.63.51.0 10.63.50.1 MASK 255.255.255.0 /P

ROUTE ADD 10.64.51.0 10.64.50.1 MASK 255.255.255.0 /P

The /P means make the route permanent (remember across reboots). The above example assumes standard class C subnets all round.

Another solution would be to configure both your routers to forward traffic heading in the wrong direction to the other router i.e. If your DSL router receives trafficdestined for your remote office network it should be forwarded to your T1 router and vice versa. This assumes that there is a connection between the two routers.

Clear as mud! Hope this helps...

by ebob

Yes, the problem is with the routing. I would back up and start from the beginning.

"IF" I understand your description, you're using the T1 to talk between your 2 sites, and each site has a DSL Internet connection for local Internet usage.

I would have only one NIC in each PC. They all come back to a switch (or hub) at each site. Each site should also have a router. Each router needs 2 interfaces: one for the T1 and one for the DSL. Then you simply create a routing table in each router that says "if this is traffic for 'the other office' go down the T1, otherwise go out the DSL".

This way you put routing where it belongs: on a router, instead of trying to organise from each and every PC. This latter approach is just going to get more and more awkward for you.

This discussion is closed to new replies.