Issue with Receiving Config 2

[lwhalo]

Having an issue with receiving the config file from my IP Office system to the Voicemail PC. The IP of the switch is 172.16.28.33 and is 172.16.28.34 for the voicemail PC. They are on the same switch and I can ping .33 from the PC. I know the password is correct because I use that password to open up MONITOR and I also get an incorrect password message when I use a different password. Here is what I get when I run Monitor when I try to open up the config:

********** SysMonitor v5.1 (48) [connected to 172.16.28.33 (_0E007020DD4)] **********

9695mS PRN: Monitor Status IP 406 DS 3.1(48)
9695mS PRN: LAW=U PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=1 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=28)
22143mS PRN: TFTPServer::RRQ(from 172.16.28.34) nasystem/who_is
31018mS PRN: TFTPServer::RRQ(from 172.16.28.34) config/$t%$'~ q
31019mS PRN: Config Write Wake Up
31339mS RES: Sat 21/2/2015 13:51:45 FreeMem=48881188(17) CMMsg=5 (5) Buff=100 635 498 560 5 Links=9586 Elements=0
31520mS PRN: IO List Size 1
31520mS PRN: Sending Config out to fef4c5bc started
31530mS ERR: TFTPReceiver Unreachable net=ac101c22 port=0xc839
31531mS PRN: WARNING:eviceConfigIO EOF during outstanding=0 len=114
31538mS PRN: Sending Config out to fef4c5bc finished
31539mS PRN: Config Write Completed

I have McAfee AV on the PC and disabled Access Protection. Is this something I can fix or is this a hardware issue?
Thanks..

 

[Gunnaro]

Disable the firewall+AV on the pc completely, the try again.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[lwhalo]

Uninstalled McAfee and also disabled all Windows Defender Options on PC. Still have the same issue

 

[sizbut]

Monitor uses a totally different password from receiving the IP Office configuration so you haven't really told use anything other than the security is working correctly and you're using the wrong password.


Stuck in a never ending cycle of file copying.

 

[Westi]

If this is a new system then go into the security settings and redo the Administrator password.
I had it happen now 8 out of 10 times that the new system is unavailable when powered up (9.0) wiht a newly created SD card and I had to go and write the security settings again

Joe W.

FHandw, ACSS (SME), expired ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[lwhalo]

I'm pretty sure the password I'm using is correct. When I try a different password in Manager, I get an error message that the password is incorrect.

 

[lwhalo]

How do I get into the Security Settings if I can't get the config file to load?

 

[Gunnaro]

I'm pretty sure this 406 R3.1 has been in use for some years
Security settings is accessed differently, though from the same application.

What about SSA, does that connect?
Maybe try another pc to access the IPO.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Westi]

Oops should have read the Monitor log better and see the 406 with R3.1

There are no security settings in 3.1 that started at 3.2 (from memory so no guarantees) which means that your password to retrieve the config is the same as the monitor password which is by default password and it shows in the log as such even though encrypted

Joe W.

FHandw, ACSS (SME), expired ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Gunnaro]

I've never even seen a R3.1
Though I thought the Security came with R3.0

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Westi]

From Prod Description of 3.2

What's New in IP Office 3.2
For those already familiar with IP Office, this page lists the new features introduced in IP Office 3.2. This is not a
exhaustive list, it covers just the major changes that are aimed at improving product serviceability and end user
mobility.
IP Office Management Software
• A new IP Office Manager that has backward compatibility with previous releases
• Increased service access security
• Audit trail to record who made system changes
• Error checking and validation of system configuration
• User rights management

I started with 1.2 or 1.3 (can't remember exactly) but those days you had to reboot when you changed a users button
I installed a call centre with 130 users and they came from a Nortel system, they were ready to kill me with pitch forks and burn me at the city limits after the first couple of days
But the reboots were faster, about 30 seconds. Still an eternity for a call centre especially when you do it 45 times in an 8 hour day

Joe W.

FHandw, ACSS (SME), expired ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[sizbut]

Wow, I didn't spot the major time travelling either. A long time since I touched anything pre-3.2.

Stuck in a never ending cycle of file copying.

 

[Gunnaro]

I'd say it's time to catch up with the evolution.
Put in a new 500v2, baffle the users with everything that has happened the past 10 years.

Who ever installed this back in the days must have been in a hurry or incredibly lazy.
Trace shows System pwd is "password" and system name has been left at default as well (0E007020DD4).

Looks like the pwd you're using is correct, but there is something going on at the VM server:

31530mS ERR: TFTPReceiver Unreachable net=ac101c22 port=0xc839

net=ac101c22 -> is HEX for 172.16.28.34 (your VM server)
port=0xc839 -> is HEX for 51257

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[IPGuru]

Monitor password & System password are not always the same
if you can locate a copy of IPOPass.exe you should be able to obtain the system password

alternatively if you have a backup copy of the cfg file then revaluation form snadboy.com should be able to reveal the password for you

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Gunnaro]

That's correct, but this trace shows:
31018mS PRN: TFTPServer::RRQ(from 172.16.28.34) config/$t%$'~ q <- That is "password" encrypted.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Westi]

in 3.1 they are the same

seems I repeat myself sometimes

Joe W.

FHandw, ACSS (SME), expired ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Gunnaro]

I think IPguru's statment was more of a general kind, not specific to R3.1.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[IPGuru]

Even in 1.0Network Alchemv V2.1 (that is as early as I go) Monitor, system & voicemail password can all be set different.

Repeating incorrect information does not make it true (although politicians would have you believe otherwise) I am surprised at you westi


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[IPGuru]

Looking at the issue downloading the cfg I would initially say Anti-virus or Firewall

another option is VPN, we used to use a VPN clinet that needed to be disabled in network properties before it would allow TFTP even when disconnected.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[lwhalo]

Here's what I did so far:
1) Installed the Admin software on another PC and tried to receive the config file.
2) I was able to receive it Ok, but whenever I made changes to the config and tried to right it back to the switch, I got an error back from Avaya IP Office Manager - Unhandled Exception has occurred in your application......
3) I was able to duplicate this error by installing Admin on another PC which told me the issue was on the switch.
4) Had a tech revert the switch to it's original settings then copy the config I saved back to it.
5) Issues still persisted.
6) Tech replaced the main unit and placed the old config and we are good to go.

Thanks for all of you that commented.