After I connect to the VPN sanbox. I try to login to the Comunications Manager (CCM) but the login fails with Database Communication error.
We are looking at this and will get back to you shortly.
Any time you loose we will add to your reservation.
Can you also send me the domain name for the windows login - I cannot
connect with either "localhost\admin" or admin user. Password Cisco.
Domain name for that lab is "abc.inc".
strange - still cannot rdp to the machines.
I tried the "mstsc.exe /v 10.10.20.30 /admin" and "mstsc.exe /v
10.10.20.30" within user abc\admin and abc.inc\admin Still no luck
Could this be the same issue as the CCM / Central LDAP issue?
Let me try from here and get back to you.
So for 10.10.20.30 I used:
and the password supplied in the portal. That worked fine.
Just be careful where the @ is on your keyboard. It can be mixed up with "
Really sorry but still no luck.
abc.inc\administrator \ ci....(password displayed within the Progger A
Resource Attributes window)
abc.inc\administrator \ Tbb... (VPN portal pass / Output information for
Not sure what you meant by the @. I must be missing something?
Now I see the issue and I do apologise. Do not use the credentials in the attributes for each resource. I am not sure how they got populated in that way but I will correct.
Instead, click on the instructions button on the topology page. An instructions tab will open on the LHS. There is a Lab Details link there. Click on it and a short .pdf will open. The credentials for each server are there.
Let me know if that works for you.
Got it thought! I was missing something. Thanks.
I just need to figure out how to connect our application to the sandbox to
do testing next.
I will look at the CUCM tomorrow morning. I am in GMT.
I can try the reboot if you like. Or would you rather wait?
Looks like a recovery disk is required. I will take a look tomorrow morning.
Unified Communications manager is back online.
I'm trying to test our CTI application against the ProggerA (10.10.20.30)
Side A is responding but Side B is not.
I verified that the services are up and running on both servers.
Verified ports via Finesses admin interface
I then attempted a quick test using a simple telnet.
"telnet 10.10.20.30 42027" worked with blank black screen
"telnet 10.10.20.24 43027" no response failed to connect
Can you confirm that the Side B is running properly.
My reservation has expired and have not heard back regarding the side b activation.
Please let me know my options.
Retrieving data ...