For the ISDN you'll need either two live ISDN lines or an ISDN simulator.
For the T1 WICs you can make a T1 crossover cable. I fergit the exact
pinout, but it should be no trouble to find it on the Internet.
- Don
-Original Message-
From: Robert M. Cramer [mailto:[EMAIL PROTECTED]]
Sent:
The T-1 WICs is the easy one. Cross pins 1&2 with 4&5 both ways and you have
it. ISDN however, requires either ISDN service from the local telco or a
simulator (read pricey). Verdors are Arca Technologies, Teltone, or Adtran
(Atlas 550 etc).
> -Original Message-
> From: Robert M. Cramer [
There is currently an article on tcpmag.com written by eric quinn that
covers the subject .
""Robert M. Cramer"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I have a newbie question regarding a home test lab:
>
>
> I have two ISDN routers 802 and 804 - Can
Stephen,
The second group of commands are much more secure, however as you know you
have restricted port access to a point that keeps out ping (Can be a good
thing!) and DNS resolution.
I would suggest opening TCP AND UDP ports 53 for DNS resolution in addition
to 25 and 110.
That should fix yo
Hi there,
Just do the following:
multilink virtual-template 1
interface virtual-template 1
encapsulation ppp
ppp multilink
... assign serial link IP address (eg. ip address 192.168.255.249
255.255.255.252)
interface serial0
no ip address
encapsulation ppp
ppp multilink
inter
Hi,
I have used almost the similar configuration to configure my Cisco AS5300 for
Multilink. It was successful but I have observed that the speed through Multilink is
slower than the single link. What could be reason.
I am using AS5300 with 4 PRIs.
Thanks
Aftab Rashid
Paul Lalonde wrote:
Yes it's an ARP issue. I bet your PIX has the following line:
arp timeout 14400 (equal 4 hours in seconds)
The other parameters for timeout settings are something like the following:
timeout xlate 1:00:00 conn 1:00:00 udp 0:02:00
timeout rpc 0:10:00 h323 0:05:00
timeout uauth 0:05:00 absolute
Well, this wouldn't be in the default configuration of any IOS rev I've
seen, but you may want to check for a "sysopt noproxyarp (interface)"
command in your configuration. Such an option, viewed as a security
enhancement, can cause the problem you're having. If you wish to use it,
you'll probab
Hie..
Well , it more than "plugging" a modem to serial interface and dialin.. You
should check
among other things -
- wether you serial port is async or sync [ you need a physical async port
for for you
to attach your modem]
- you 'll need to configure your router to accept CHAP or PAP dialin
How do you intend to bring up a dead router through an attached modem. Do
you mean if an interface goes down?
-Original Message-
From: Brian Fitzpatrick
To: [EMAIL PROTECTED]
Sent: 18/06/01 12:11
Subject: Newbie Question [7:8933]
Hi,
how do I set up a router with a dial in modem? Is it
Very simple.
Attach the modem with the proper adapter and cable to the AUX port of the
router.
Configure router as follows:
Line aux 0
modem dialin
login
password cisco
transport input all
speed 115200
flow hard
modem autoconfigure type usr_sportster (or whatever type of modem you are
using. The
Internetworking Technologies Overview on www.cisco.com.univercd and in book
form does a beginning explanation of the WAN technologies and if you combine
that with the BSCRAN CCNP book , you'll have a good understanding.
--
RFC 1149 Compliant
""Mahmood"" wrote in message
[EMAIL PROTECTED]">news
1.) Read Cisco press
2.) Go to www.cramsession.com
3.) Buy the boson tests
4.) Buy some real routers and switches on ebay or ubid
--- Mahmood wrote:
> Dear Friends,
> I'v studied CCNA, But I have so many question that
> can't find in the ccna books.
> I need to get a big picture about wan te
I resently passed the CCNA 607 test using 507 material. Cisco Press (ICND),
Todd Lammle's CCNA Study Guide, RouterSim and the Boson test prep. I read
both books and had the same problem of understanding the big picture and how
all of the 'technologies' worked. I sat down with Todd Lammle's book
You should be able to ping the local end if your using point-to-point
subinterface. For multipoint and no sub-interfaces you need to use a local
mapping.
Regards,
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of iancu
mihai
Sent: Saturday, May 13, 20
You have to map your local IP to your DLCI in order to ping.
Do the " show frame map" to verify if you have a map for your local DLCI.
Henry
-Original Message-
From: Joe Karpenko [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 14, 2000 5:53 AM
To: [EMAIL PROTECTED]
Subject:
I had the same situation a while backI was able to ping the remote
interface address but not the local address; my issue had to do with 2
MC3810's that
weren't running the same IOS; I upgraded to the same IOS and then everything
was just fine:: that is if both your local/remotes are the same s
jw,
When using Frame Relay the router will have:
- a physical access circuit (this is the circuit between the router and the
Frame Relay provider, i.e. T1)
- a PVC or SVC (this is the "virtual" circuit through the Frame Relay cloud
to the other router)
The physical access circuits can be diffe
Mike
First of all, thanks for your reply.
I didnt know there was such a thing as physical
access circuit going to providers access switch. All
I was thinking as a connection mechanism was PVC.
I understood that central routers sending rate could
be different from branch offices receiving rate
Well, if RouterA can ping the ethernet interface of RouterC, then it
will also be able to ping any workstation on that ethernet segment
provided that the workstation has a correctly assigned IP address, and
default gateway (Should be set for RouterC's ethernet IP address).
If RouterA cannot ping
Ahhh Yes Alan, you are right. Setting the router's
interface as the default gateway on my workstation is
what I didn't do properly. Thanks
Cisco Boy
--- "W. Alan Robertson"
wrote:
> Well, if RouterA can ping the ethernet interface of
> RouterC, then it
> will also be able to ping any works
Ask yourself three questions;
1. can router A ping the far side of router C
2. are the workstation and router C in the same vlan
3. is the workstation configured for a default gateway of router C's near
side interface?
If you can answer yes to all these questions you should be able to go ping
craz
22 matches
Mail list logo
