CallPilot 2.0 Not Recognizing LAN ...

[JustShady]

We have CallPilot 2.0. During recent server room cleanup, the LAN cable was removed and when replaced CallPilot was no longer accessible via CallPilot Manager over the LAN. We do have access via a connected monitor and keyboard but I do not want to leave the cabinet open and would rather have access from my desktop in my office. Do I need to reboot CallPilot and when I do will I need a password other than the one we use to set up new users etc.?

Thanks in advance,
JustShady

 

[sandyml]

Check your connections again, and perhaps try another cable. Normally you shouldn't have to reboot your CallPilot. But if you do, you will need the server logon passwords (ngensys and/or ngendist accounts).

 

[johnpoole]

before i tried a reboot i would try to ping from the sever to the default gateway, a simple cable change should never require a reboot, make sure the cable you removed was not rolled, if you need help with network commands just post them here, or any desktop admin geek will know a few million, might just need to toggle the nick using the admin software

john poole
bellsouth business
columbia,sc

 

[JustShady]

According to the network tech who moved the cables CLAN is what he reconnected. ELAN was connected to an OTM PC thru a Lynksys Hub along with an AUI from the switch. It is my understanding that LAN access to CallPilot is thru ELAN. Is this correct? The cable connected to the OTM PC went to a two port NIC and I believe the second NIC port was connected to the LAN.

Thanks for your help guys.

Scott

 

[sandyml]

The CLAN connection is what you need to work in order to access the Call Pilot from your office. Can you ping the Call Pilot's CLAN IP address from your office? From the Call Pilot server, can you ping the default gateway on your LAN? Are the ends of the cable firmly seated? (It sounds stupid, but it happens pretty often.) If you have a laptop, give it the IP address of the Call Pilot CLAN, and move the CLAN cable to it. If you can ping it, then you may have a bad NIC card or some other issue with the Call Pilot; otherwise, the problem is the cable onward to the LAN. Let us know how it goes.

 

[JustShady]

Thanks to all for the support.

As suggested I set my PowerBook to the CallPilot CLAN IP address and tried to ping from elsewhere on the LAN. No luck.

The cable was not properly seated into the switch port. Reseated cable, pinged okay.

Reconnected to CLAN and tried ping again, no luck.

Stopped and restarted IIS Admin Services and World Wide Web Publishing Services. This seamed to do the trick although we think that just restating the

http://WWW Pub

Serv would have done it.

Any thoughts?

We are now able to access the CPManager via the LAN again.

Life is good.

Thanks again.

Scott

 

[sandyml]

Good to hear you got it back up. Sounds like the CLAN cable connection started the whole thing, and then CPilot just got confused from there. Thanks for letting us know you're ok.