Problems connecting to 406 running 4.2(17) using 6.2(17) manager

[rm81]

Hello everybody,

I've recetly upgraded a customers 406 ds to 4.2(17)along with upgrading to the latest vmpro.

As part of the upgrade i also upgraded the manager, however since the upgrade i cannot access the system via our isdn pc, i have upgraded our manager to 6.2(17)when i browse for the ipo the system appears i enter the correct logon credentials but get a network error and the dial up disconnects, all other customers units are visable and i am able to connect.It just seems to be a problem on this one site since the upgrade

I have checked the discovery preferences and inputted the correct address ranges my understanding is that when Open configuration is selected,It performs a UDP broadcast to the address 255.255.255.255. This broadcast will only locate IP Office systems that are on the same network subnet as the Manager PC, the unit appears to be on the correct range, i have also connected to a manager pc onsite via logmein rescue and cannot see any differences on the discovery settings.

Could anyone perhaps shed any light on this as i'm out of ideas, many thanks for your time

 

[jamie77]

Use logmein to reboot the system first off.

We have 4.2(17) systems that we connect using ISDN with no issues.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!

 

[rm81]

Hi Jamie thanks for replying,

I carried out a timed reboot at 21:00 last night but still had no joy recieved "communications Error"

Very strange as the manager discovered and accessed the system with no issues prior to the upgrade which is the only obvious change.

The IPO sits on an address of 192.168.50.220

 

[amriddle01]

rm81, has something similiar but in my case I just got a communication error though it didn't drop the connection, the only way I was able to solve it was after connecting don't open the config, send the latest copy of the .cfg to the unit I could then get in, you then need to remake the last changes you did as they will have been overwritten.

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[rm81]

Hi Amriddle,

Thanks for that i've just done that will post back and let you know on the progress i didnt think to try that

 

[IPOfficeIreland]

try also putting in the actual ip of the pbx and not leaving it to the broadcast 255.

 

[rm81]

Hi Guys,

Many thanks for the input very much appreciated just to confirm i have sent a saved copy to the unit (reboot when free)i have also tried connecting directly to the ip address recieved "service command failed error code 2".

Discovery preferences are set to TCP and UDP enabled
System IP address 192.168.50.220, IP search criteria 192.168.50.223-192.168.50.221, Connecting IP address of 192.168.50.222.

406 responds on ping request average of 204ms.

Just wondered if i am missing something

 

[tlpeter]

Your search criteria is not right but that should not give you this problem

ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[rm81]

Hi tlpeter,

I've just reset the search criteria it appears i can send a config to the unit as suggested by amriddle earlier on in the thread but am unable to recieve.

Just to rule out any internal issues i connected to the unit directly from our remote access pc not via rdp still no joy although i am able to connect to and recive other site config's without issue.

again many thanks to all

 

[tlpeter]

Did you upgrade form 3.2 perhaps ?
The password is changed and the login is:

Administrator
Administrator

ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[amriddle01]

Try a power down reboot sometimes the LAN ports go funny on 406's

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[rm81]

i upgraded from 3.0(59) and indeed the password has changed
however i still cannot log in very strange

 

[rm81]

Hi again all,

We've pretty much tried everything now on this one only option left is a power down at the end of the day.

Deleted the firewall profile(as advised by distributor) tried different ip routes still no joy, even went down the route of defaulting the security settings.

Pray the reboot works or i have a nice long drive ahead of me

 

[jamie77]

In the Dial Up, click properties>Networking. Highlight TCP/IP and click properties. Click Advanced and untick Use Default gateway on remote network.

If you are not local on the machine, using remote G/W will cause connection issues.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!

 

[rm81]

Hi Jamie thanks for your reply,

I checked those settings and use default gateway on remote network is unticked we have it set this way as it causes issues with our rdp/ts connections to that particular isdn pc.

Only thing i can think of is to attend site and default the config restore a known good working copy and retest.Or failing this do a clean rebuild of the config.

 

[mattKnight]

The perils of remote upgrades...

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.