Search results for query: *

Got it worked out - someone had changed the prime set DN!

I've also confirmed that the auto attendant is still turned on and is set to answer line 241 after 0 rings. I've tested the auto attendant on other lines and greeting table combinations and it works fine.

Hello All, I have a Nortel BCM 400 with integrated call pilot and I have an unusual problem. Our main number, line 241, should be answered by the auto attendant. Sometime this afternoon the auto autto attendant stopped answering calls and they started ringing to the receptionist's intercom...

Thanks but the way the Dell ML6000 works is both the drive and the changer have the same SCSI ID and then it uses LUNs to differentiate the drive from the changer. This is the first device I've ever setup like that and am having a hell of a time getting everythign working. Even after I've...

Hello, Did you ever figure this out? I'm haveing the exact same problem with a Dell ML6000 and a single drive. All tapes are seen as cleaning tapes after an inventory. Thanks!

Thanks for the help guys - I got it working by enabling RIP on the new core and just keeping the single default route on the new remote. I'm still not 100% sure why this worked so I'm gong to study the rip gererated routing table. Thanks for all the help! --KK

The Alarm light should be on at all - you're going to have to get back on the horn with the ISP.

What lights are illuminated on the back of your WIC T1 card?

Sounds like it could be a physical layer 1 problem. I'd check the wiring on the jack if it's been extended from the smart jack at the demarc

I'm not really sure what you mean so I tred to take the IPs out of the equasion. The default on the remote is now: ip route 0.0.0.0 0.0.0.0 Serial0/0/0 and show ip route looks like: Gateway of last resort is 0.0.0.0 to network 0.0.0.0 192.168.50.0/24 is variably subnetted, 2 subnets, 2...

new core is connected to C 192.168.1.0/24 is directly connected, GigabitEthernet0/0 and default route is to 192.168.1.1 - I thought that would take care of it. From the new core I can ping 192.168.1.1 (old core internet sites - routed through the old core) Thanks, I've changed the duplex...

No go, when I try that I get: Lakewood-Router(config)#ip route 0.0.0.0 0.0.0.0 192.168.50.2 %Invalid next hop address (it's this router) 192.168.50.1 is serial on core 192.168.50.2 is serial on remote Thanks!

New core: Gateway of last resort is 192.168.1.1 to network 0.0.0.0 192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks C 192.168.50.2/32 is directly connected, Serial0/0/0:0 C 192.168.50.0/24 is directly connected, Serial0/0/0:0 C 192.168.1.0/24 is directly connected...

Okay, I've chanted them back to the same subnet and changed the route in the core too: ip route 192.168.3.0 255.255.255.0 192.168.50.2 interface Serial0/0/0 description "AT&T T1 XXXXXXXXX" ip address 192.168.50.2 255.255.255.0 encapsulation ppp ! interface Serial0/0/0:0 description...

You're right they are not. Origionally I had them on the same subnet 192.168.15.1 & 15.2 but read somewhere that they had to be on a different subnet - I've tried it both ways with the same result.

I've been beating my head agains the wall for a day no trying to get this to work. I'm in the process of upgrading our WAN by replacing the core router and all the remote routers and adding additional T1s. I'm working on the first remote site now and can't get the routing correct. Relevant...