• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 304
  • Last Modified:

Cannot connect to network through point to point T1 connection?

Greetings,
The company I work for has a lan and internet access is through a T1 line, at location A.  We recently had the T1 line extended through a point to point circuit to location B.  I need to set up a pc at location B which is connected to our lan at location A.  I have tried to install a hub connected to the Cisco 1700 series router that SBC left after hooking up the point to point T1 at location B.  When I connect the pc to the hub and try to run the network setup on the floppy, it keeps telling me that it cannot connect to the domain.  Location A has a server running Windows 2000 small business edition and all the pc's on the network use Windows XP pro.  I have tried both patch and crossover cables to attach the hub to the Cisco router and have also tried to connect the pc directly to the Cisco router using both patch and crossover cables.  No matter what I do, it never is able to talk to the domain at Location A???  Since I am not a network person, I really don't have any idea what to do next?  SBC does not respond either.  I don't know if I need a different piece of hardware like a switch or something or if I just don't have a clue as how to set up a pc at location B to connect to our main network at location A?  Please help if you can.  This is a time critical project and I am stuck.  Thanks!
0
mjchevalier
Asked:
mjchevalier
  • 2
  • 2
1 Solution
 
stzinCommented:
have you tried pinging location A from your host on location B? did you verify the IP address of your host in location B to make sure it is on the same subnet as Location A?is the defaulty gateway on the host in Location B setup properly?
0
 
mjchevalierAuthor Commented:
Thanks STZIN, but no I have not tried to ping or anything yet.  Can you please describe how to make sure it is on the same subnet and how I can tell if the default gateway on the host in location B is set up properly?  Thanks!
0
 
stzinCommented:
I've just re-read your post. If understand your setup is like this:

LocationA <-LAN--> Cisco RouterA <-T1-> Cisco RouterB <-LAN-> LocationB

Is this right?

If so, then im guessing the routers were setup correctly to communicate. If so, the router in LocationB should have an IP address and subnet mask. You have to find out what these are. Let say its:

IP: 10.2.1.1
Subnet Mask: 255.255.255.0

The your host in Location B should be:

IP: 10.2.1.x (anything greater than 1)
Subnet Mask: 255.255.255.0

First test to ping your router: open the command prompt (start>run>cmd and press enter or type command depending on the O/S).

ping 10.2.1.1. (or whatever the IP of the Cisco router is in Location B)

If you get a reply then you're on the same subnet as the Router in Location B. Which is good. Now try pinign a host in Location A

ping 10.1.1.x (where x is an IP address in Location A - remember i'm just using 10.1.1.x as an example, the subnet Location A may be on might be totallly different, but basically all you need to know is the IP address of a host in Location A).

So again, If you can ping your Router in Location B and you know of an IP address in Location A then try pinging the IP address in Location A:

ping 10.1.1.50 (as an example).

if you get a reply then you're done. if not could be many things. First thing though would be the routers config to properly communicate with Router in Location A. Who setup the Cisco Router in Location B? I would call this person if and only if you can finally ping Router in Location B but cannot ping a Host in Location A.

Good Luck.

0
 
mjchevalierAuthor Commented:
Hi STZIN, your assumptions are correct except that all I have at location B ends at the Cisco router(CSU/DSU).  I tried to connect a hub directly to the Cisco router and then tried to connect a pc to the hub and configure it as part of the lan at location A.  Does this change your ideas at all?
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now