Multiplicity generated problems with my Terminal Server service.

What OS are you using?
What version of MP?

An added question - are you connecting via VPN (pix-to-pix)by chance?

I am not sure of the architecture of multiplicity but I will do some research to see if I can help.

The server is windows 2003 server Service pack 2 and multiplicity was installed with version Multiplicity 1.02 Professional.

The problem now is very weird, I don't really know if multiplicity had something to do... but Terminal Server works on the lan but no through Internet.... ???

But the weird thing is that I was connected to terminal server. Installed, rebooted & lost lan access. Uninstalled multiplicity and then I regained LAN access to terminal server but couldn't access from Internet... any clues? Still having that problem.

We also run the same Terminal Server setup. As you know there are a lot of things that can cause of access.

Did you check your event logs to see what the server recorded at the time of WAN loss?

Can you tell me what you are using multiplicity to do?

MP only does one thing 

The ports taht termserv uses could be blocked somewhere.

In all honesty, I'm getting a bit lost.  With MP uninstalled you can or cannot use TS?  Internet or lan?  Both?  Neither?
Now with MP installed what can you do/not do?

ZubaZ - I am not familiar with Multiplicity that is why I am asking. I can try to duplicate the problem on one of our servers to help.

Edit: Okay I know now. I would not recommend using this program especially if you are in a domain environment with trusts setup between servers. If you are running multiple servers use hardware for keyboard and mouse emulation.

  No harm.  For more info: https://www.stardock.com/products/multiplicity/

If I'm reading teh problem coorectly (and I'm not sure of that) PC1 adn PC2 are running MP to share keybaord and mouse.  But, when using TS on PC1 (or 2), MP works but TS doesn't.

I use MP on many PCs in my lab and connect via Remote Desktop (rebranded and improved TS for XP and Vista) with no issues.

More info would be useful.

Well I agree - I am not totally sure either what is going on. I think the problem is not the LAN side but the WAN side. However - the preferred method has always been hardware for KVM emulation due to port collision problems.

Here is the Multiplicity site - maybe some help there.

WWW Link

Moderators, please correct the topic as I'm giving a big statement that now is very dubious.

The problem with TS not working on the WAN, as one of you said, resulted true: DHCP was activated on the server (VERY bad move) and the firewall was redirecting TS request to an IP, so DHCP got another IP after I restarted from installing Multiplicity and generated that problem.

What still I don't have any clue about is this:

I always connect to the PC that I installed Multiplicity as the passive PC on via TS on the LAN (and consultants from the outside).
I was using it. Installed Multip and BOOM, couldn't connect anymore.

I'm not so confident to blame the soft after what I saw on the WAN problem, but is VERY weird.

Any clues on why this happened? I want to install multiplicity but I can't risk 2 servers for my confort.