Re: TCP Problem with DR system

One at the beginning:
Software problem data for QTGCONV has been logged. Refer to help text for
* additional information.
and then:
Software problem data for QTMFCONV has been logged.
Software problem data for QLZARCOV has been logged
L2TP server unable to start due to configuration errors.




From: Frederick Boniholmes <seft2011@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 12/12/2014 03:11 PM
Subject: Re: TCP Problem with DR system
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Do you receive any error message when you are trying to start host
servers?


On Fri, 12 Dec 2014 14:42:43 -0600, broehmer@xxxxxxxxxxxxxxx wrote:

I have a question that maybe, if I'm lucky, can be answered by someone

who

has
had this happen to them before I have to recreate the DR system from
scatch.
On a disaster recovery box TCP hostservers don't show up after restoring
from the production box. The DR system was a complete working system
before
the restore and now, while one can ping from the DR box to the Production

box
no hostservers are shown and none can be started and client access does
not work.
Given that something is terribly wrong with the restore, how can one
reinstall
TCP hostservers or is this even worth trying?



"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the

attachments accompanying it) contain confidential information belonging to
the sender. The information is intended only for the use of the intended
recipient. If you are not the intended recipient, you are hereby notified
that any disclosure, copying, distribution or the taking of any action in
reliance on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the law.
If you have received this transmission in error, please promptly notify
the sender by reply e-mail, and then destroy all copies of the
transmission."