VPS - Dark Screen

In short, I'm testing multiplicity as a solution for some of my small business clients.  They are looking for something more reliable than just regular windows RDP. So after purchasing the $100 package, this is my setup and outcome:

- I run 1 VPS windows server r2 2008 at the datacenter that is behind a router.  That windows is connected via VPN to the router and the router running the VPN to the office

- I'm able to successfully run the Windows RDP in that way

- I install 'slave' on Windows 2008 r2 VPS at the data center / opened the firewall and all the ports for it as a test

- I was able to connect, BUT i get black screen on the 'master' machine which is located at my office.

- I see that Multiplicity created its own rules on the inbound of the Firewall on both machines

- Running a packet sniffer, i started seeing that the second there is an established connection more connections trying to establish but fail, despite the system is listening to those ports.

 

My questions is, why is it happening?  What seems to be the issue? And when it asks for connection not to be on public, is that because its using Windows Group to connect?  I short, please provide detailed description of connections between the two machines.  I would be shocked to hear that KVM will not work on VPS given some of the recent posts i've seen.

***NOTE: For clarity:

- VPS is Windows 2008 r2 Server where the 'secondary' resides

- Windows 7 Ultimate where the 'master'resides

Thank you.

20,226 views 7 replies
Reply #1 Top

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #2 Top

How long does a client have to wait for a reply to his issue? Is this the type of support to be expected from StarDock support team?

Reply #3 Top

Hello,

Sorry to hear you are having trouble.

Quoting tumbledome, reply 2

How long does a client have to wait for a reply to his issue? Is this the type of support to be expected from StarDock support team?
End of tumbledome's quote

Like many, we are catching up after our company holiday break, tumbledome.  Sorry for the delay, however.

- I run 1 VPS windows server r2 2008 at the datacenter that is behind a router.  That windows is connected via VPN to the router and the router running the VPN to the office
End of quote

Just as long as the Multiplicity (MP) rules are set on each PC / VM, and they are on the same subnet (vital), it should be fine.  If the IPs are static on the remotes / Secondaries, however, I would recomend using IPs (instead of hostname) in the connection setup to ensure it uses the same subnet as the Primary (the one connecting to it):

- I was able to connect, BUT i get black screen on the 'master' machine which is located at my office.
End of quote

Just to be clear, that you get a black screen does not mean it is not connected - it's something else.  

If when you are connected via MP, and you do a Ctrl + Alt + Backspace (equivalent of Ctrl + Alt + Del when on a Secondary), do you get the expected rendered 'Lock, Switch user, Sign out...' etc,  or no you still get a black screen / nothing happens?

If not:

- I'm able to successfully run the Windows RDP in that way
End of quote

If you have an existing RDP session open, then use MP to KVM connect, do you still get the black screen?

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #4 Top

If when you are connected via MP, and you do a Ctrl + Alt + Backspace (equivalent of Ctrl + Alt + Del when on a Secondary), do you get the expected rendered 'Lock, Switch user, Sign out...' etc,  or no you still get a black screen / nothing happens?

Nothing Happes... I ran a batch for firewall that you guys provide on both ends, and nothing happens.  The black screen is still there and on the secondary machine I see nothing other than just the multipclity config screen.

So in short, the MP connects, establishes connection.  ctrl/alt/backspace do not work nor responds. I'm presently connected via RDP while trying to configure KVM, and nothing happens.

Reply #5 Top

Ok... Got it connected.  Seemed as there was an issue to Domain/Private/Public.

My next question:

 

I would like to know if it is possible for 2 MPs to connect to 1 secondary and have a shared session.

Reply #6 Top

tumbledome,

Quoting tumbledome, reply 5

Ok... Got it connected.  Seemed as there was an issue to Domain/Private/Public.
End of tumbledome's quote

Very glad to hear that.

Quoting tumbledome, reply 5

I would like to know if it is possible for 2 MPs to connect to 1 secondary and have a shared session.
End of tumbledome's quote

There is not, no.  If one is KVM connected, and another connection is initiated, the first will be bumped off. 

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #7 Top

Thanks for the explication. I didn't know that the first will be bumped off if one is KVM connected and another connection is initiated. I recently opened my site and needed support from a reliable linux vps. I don't have a budget for an assistant who will do all this work, so I had to figure it out independently. Actually not as tricky as I expected, but I faced specific difficulties. Fortunately, there are many tips on the forums, including your advice. Therefore, I am grateful for every feedback on this topic that helped me to establish a workflow.

+1 Loading…