I have a very simple project which for some reason is becoming very difficult (probably because I don't know what I am doing), but anyway. We just leased a point-to-point T1 and have a Cisco 2600 on both ends. All that I want to do is have the network on the far end of the T1 think that it is part of our network. I.E. I simply want the two routers to act like bridges and connect the remote end so that it can register with our dhcp server and use our internet connection. We have have a small network so there are no access-lists or tricky security considerations. We are using an internal class b addressing scheme for the network, again nothing tricky. If you could give me some basic configuration suggestions I would really appreciate it.
Without knowing what problems you're running into, it's tough to know what's difficult. I'll just spout some stuff off and hope it helps ... :)
UDP broadcasts are used to locate network services such as NT Domain Controllers, DHCP, DNS, and BOOTP. However, routers do not forward UDP broadcasts by default. In order to provide access to these services across the WAN, each remote Ethernet port on the router may require an IP Helper address to forward UDP broadcasts to the appropriate server.
Make sure your subnet masks are correct. Can you ping both router interfaces from the local subnets? If you can, then we can look at the T1 setup.
The actual problem that I'm having is that yes I can ping from the remote client to the server and if I manually give the remote machines an IP address they can login without any problems. However, if I set them to automatically obtain a ip lease from the dhcp server they are unable to find it. I tried putting the IP helper address in and it didn't seem to help. And no I'm not sure that the subnet masks are correct and would appreciate any advice. Our dhcp server address is 10.60.1.10 255.255.0.0 and I have the range of 10.60.1.1 255.255.0.0 through 10.60.1.254 reserved for equipment. If you don't mind, could you give me sample of how you would do it, including subnet masks. Also the rest of our network, because it is small, is using RIP. Is this a problem?
Just change the example 192 network addresses with your 10 addresses to get a feel for what the diagrams are trying to convey.
Yes, you might be new at this network thing, but if you set it up right, you will surely save yourself trouble later on. Write out a plan, cut out a DHCP scope, and subnet your network and you'll be cooking. Most important, look at "NetBIOS over TCP (NBT) " in the first referenced link above.
Knowing what you are running on your 'near end' LAN would help - but I would not bridge. Traditional LAN broadcast over T-1 is usually not wise.
If you can (I assume you can) - subnet your private address space and route your datagrams between subnets. Use 'ip helper' on the far end to forward your DHCP requests as unicast or broadcast. Create def. route on far end.
This all assumes you are using private address space and use NAT.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...