MP has become slow to reconnect

I am using MPP to control my test machine from my development machine. I have two NICs, one for regular network traffic and the other dedicated to remote kernel debugging. When something happens to cause the test machine to blue screen (of course it's always someone elses code since mine's perfect ) and the test computer reboots, MPP on my development machine won't reconnect. This seems to have started when I added the second, dedicated NIC, though the OS doesn't see it as an available NIC to configure. VisualSoftIce takes complete control of it: I.e. ipconfig /all doesn't list it. The only way I've been able to get it to reconnect is to configure that secondary machine.

I'm using Win XP Pro SP2 and MPP 1.02.006. If there's any additional information that would help, let me know.

Thanks,
Mark

Also sent to support@stardock.com
3,759 views 5 replies
Reply #1 Top
Configure on the primary machine, or on the secondary?
Reply #2 Top
Configure on the primary machine.

Mark
Reply #3 Top
Sounds like the IP is dynamic.  Have you told MP to look up the IP everytime?
Reply #4 Top
Must . . .not . . . make . . . Aggie . . .joke . . .


Posted via WinCustomize Browser/Stardock Central
Reply #5 Top
Neil:
No, I have that unchecked and have hardcoded the IP address. Even though it is theoretically dynamic, it doesn't change. Should I change this? Something else I though of that I don't know matters is the development machine has been added to the domain, and the test computer hasn't.

Zuabaz:
That's ok. I tell them myself.

Mark