I've got a 2 system SCN with 406V2's running 3.1.65 and centralized VMPro. The customer is using a remote access software called RealVNC to access the VMPro computer and make changes. This is something that their data vendor set up for them. After making some minor changes and merging the config at their remote location, the system crashed. And when I say crashed, I mean dead! You can't even get into through the DTE port. This has happened twice. You can make changes all day long directly from the VMPro pc, but as soon as you do it through the RealVNC program the system gets fried. Has anybody else out there experienced anything like this? We have many customers who use the Windows Remote Desktop to make changes on IPOs and have never had a problem. Does anybody know anything about RealVNC or have any idea why this would happen? Any incite that anyone might have would be appreciated. For obvious reasons, the customer is not happy and wants some answers. The only common denominator here is the RealVNC software. Thanks in advance.
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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
RealVNC remote software crashed my system!!!!
- Thread starter gnmsnyder
- Start date
mattKnight
Programmer
Don't! Sooner or later it will corrupt your Voicemail Pro (it is a known issue)!
What system?, what version of software? What happens whe this problem occurs. How are you connected?
Take Care
Matt
If at first you don't succeed, skydiving is not for you.
- Thread starter
- #3
Never heard about the Windows Remote Desktop corrupting VMPro. Good to know, but in this case they aren't using that. They are using RealVNC.
The system in an IP Office. Both sites are 406 V2 running 3.1.65 software. They are connected through an MPLS circuit provided by a company called Paetec previously USLec. When the problem happens the remote system gets fried. Customer has made two changes at remote site through this RealVNC software and after merging the config the remote IP Office completely crashed both times.
The system in an IP Office. Both sites are 406 V2 running 3.1.65 software. They are connected through an MPLS circuit provided by a company called Paetec previously USLec. When the problem happens the remote system gets fried. Customer has made two changes at remote site through this RealVNC software and after merging the config the remote IP Office completely crashed both times.
IPOfficeIreland
Technical User
stopped using vnc about a year ago, use logmein instead. more stable and secure platform. remote connections to the voicemail system currupt the service, you will notice a load of rubbish on the start up screen when you open the program first.
don't think avaya support it either. But log me in is great, throw out vnc.
don't think avaya support it either. But log me in is great, throw out vnc.
- Thread starter
- #5
Yeah, I've already told the customer to never use it again, but I don't understand how it's just completely destroying the remote IPO. I've never seen anything like it. Any idea where I can find more info on the danger of remote connections to the VMPro?
If centralized voicemail is used then ther emust be a connection between those ipoffice's
How are they connected and why isn't that connection used to manage the ipoffice with manager ?????
ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
How are they connected and why isn't that connection used to manage the ipoffice with manager ?????
ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
- Thread starter
- #7
That connection is being used. They are connected through an MPLS circuit as noted above. The system manager is located in their Richmond office and is administering their VA Beach location through this circuit. VMPro is located in Richmond. The main VM pc is located in the basement. For their convenience they had their data people set up a remote connection using RealVNC to the VM pc from the Administrators pc upstairs. When she makes changes from her pc in Richmond, through the remote connection which goes through the MPLS circuit to the VA Beach IP Office, the system gets fried.
mattKnight
Programmer
I missed a bit on my last post!
I've not ever experienced a problem with VNC...
Take Care
Matt
If at first you don't succeed, skydiving is not for you.
I've not ever experienced a problem with VNC...
Take Care
Matt
If at first you don't succeed, skydiving is not for you.
I have never had a problem with vnc and wonder why you think that vnc is the culprit.
If manager is on the vmpro computer and you use vnc to see and use the desktop of the vmpro computer then all should be fine since it is that manager application the makes the changes to the ipo and not vnc. Vnc simply lets you use the console session of the vmpro computer.
If manager is on the vmpro computer and you use vnc to see and use the desktop of the vmpro computer then all should be fine since it is that manager application the makes the changes to the ipo and not vnc. Vnc simply lets you use the console session of the vmpro computer.
I use VNC regularly and have made 100's of merges through it and have yet to have a problem. I don't see any correlation between VNC and an IPO "frieing". Not making sense to me. I've used logmein w/ equal success.
Can someone please shed some light on the remote desktop "known issue".
Figure it out damn-it!
Can someone please shed some light on the remote desktop "known issue".
Figure it out damn-it!
kurthansen
Technical User
I found where it says remote desktop will mess up voicemail pro:
But it also says that if you do the mstsc /console /v:IP_Address you will be fine.
I also am using VNC with other clients and never had a problem yet.
But it also says that if you do the mstsc /console /v:IP_Address you will be fine.
I also am using VNC with other clients and never had a problem yet.
I use VNC all the time. It works pretty reliably and is a relatively small problem. It does, however, increase CPU load a little.
RealVNC can have problems. I use UltraVNC instead.
It gives you direct console control and allows you to transmit files to and from the server/workstation.
I'd also have to question VNC being the problem for the crash. I too have merged systems. I even purposely pulled the reset the system in the middle of the config upload. All I had to do is is the usual ATX commands and I was back in business. Sounds like a coincidence to me. You should always be able to get to the system through the DTE port. We use it for servers that have nothing to do with IPO and all is well.
Try Ultra. I believe it is much more stable and has an encryption tie-in.
Drew
RealVNC can have problems. I use UltraVNC instead.
It gives you direct console control and allows you to transmit files to and from the server/workstation.
I'd also have to question VNC being the problem for the crash. I too have merged systems. I even purposely pulled the reset the system in the middle of the config upload. All I had to do is is the usual ATX commands and I was back in business. Sounds like a coincidence to me. You should always be able to get to the system through the DTE port. We use it for servers that have nothing to do with IPO and all is well.
Try Ultra. I believe it is much more stable and has an encryption tie-in.
Drew
ipofficeman
Vendor
Used Real VNC for a long time, on many systems, without a problem and will no doubt continue to do so.
but...
Ultra is far superior and as Drew mentioned, it has the encryption plugin, supports file transfer and is a much cleaner install.
RDP is good, but sometimes I wonder if it's any better than installing a small app such as vnc, especially when you know of the issues with RDP.
but...
Ultra is far superior and as Drew mentioned, it has the encryption plugin, supports file transfer and is a much cleaner install.
RDP is good, but sometimes I wonder if it's any better than installing a small app such as vnc, especially when you know of the issues with RDP.
I've never had a problem with either RDP or RealVNC.
Only thing I have ever noticed is spash screen usually shows rubbish on RDP connection to VM Pro. Usually when the VM PRo is on a Server OS.
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
Only thing I have ever noticed is spash screen usually shows rubbish on RDP connection to VM Pro. Usually when the VM PRo is on a Server OS.
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
- Status
Similar threads
- Locked
- Question
