Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Administration NOT CONNECTING,HELP!

Status
Not open for further replies.

guestworks

Technical User
Jun 3, 2002
47
CA
Hi,
I am using the Partner Acs Remote Admin.software and am finding that out of four Partner Acs Processors, two will not connect to Extension 76 for Remote Access.

I transfer to extn 76 and can hear the modem ,connect but do not get the password box and then get a message, "Session initiation with the PARTNER system has failed."

Is there ANY way to reset the Modem on the Processor?

All the Processors are New and shipped from Avaya.
I am using the Silver coloured Pcmcia card.
I have tried both PC slot 1 and 2.
I have assigned a password in #730.

As I mentioned before, I can connect to the other two Processor, so my computer works using the software.

Any Ideas will be welcomed!
 
There's no reset for the modem, short of a power cycle. That won't help your cause.

There's a few things you can do to connect to those problem sites (I maintain ~450 Partner sites, so I do a lot of remote modem dances during a day's time).

First, be sure your port speed on the PC is set for no more than 38600. If it's at the default of 115000, you can get a carrier without a robust data transfer. Then it'll just sit there and do nothing, while you mutter "give me a password box, give me a password box...." under your breath.

Next, for those sites that connect, but don't initialize a session, back off your modem speed to 4800, then 2400 then 1200. Sounds awfully slow, but I'll take a translation image sent or received in 10 minutes (vs. 3 minutes) every time compared to no connect at all. I've not had a single one I couldn't connect to at 1200, no matter the mine field of bad facilities, load coils, wet cables or multiplexed lines (thanks PacBell, US West, Qwest, SNet!!!).

Also, manually back up the system translations to the card. I've had times when the password wouldn't be accepted, then did once the PW was saved in a #124.

Be sure you're running R5 remote software: there were connection bugs in the R1, R3 and R4.

Finally, there was a serial number run of 308s that, when placed in slot 1 of a 5 slot carrier, will not allow the remote maintenance modem to connect from other than an internal port. I've seen the TIB on Lucent's board about 2 years ago, and I can't find anything about it anymore! Avaya has no records of the recall effort, but they were released just as the R3 CPUs hit the streets. If you suspect you have a bad one, swap it in your carrier.

That should do you. Good luck!
 
Hi 392,
Thanks for the prompt reply.
I actually went through the tips and found something on page 6, a post on 05/28/02.

I reset the Processor and connected at 1200 baud from my PC as advised on the post, using procomm.Got garbage.


Recycled the power and dialed 76 using the Remote Admin. software. Got connected at 1200 baud and got my Password Box,,,,,hooray!

Thanks again for your prompt reply!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top