Unable to Connect via HOSTNAME only IP

connection issues

from Stardock Forums

Hi.  I have 2 x Windows 10 PRO PC's, both have fresh installations of multiplicity.  I can ping each machine and can connect to each other via remote desktop RDP so Im confident connectivity is OK.  I have Norton 360 AV installed.  The "master" can see the slave via IP and cannot resolve the hostname or mac.  I can add the slave to the master grid, however I cannot connect.  I have disabled N360 to take that out of the picture - makes no difference.  Both PC's are on a common ethernet network and set to 'private network'  - any troubleshooting suggestions welcome.

multiplicity
17,116 views 8 replies
Reply #2 from Stardock Forums Top

Hey.  The forums are mostly community driven.

Do the secondaries have multiple IP addresses?

Contact the support team at https://esupport.stardock.com/index.php?/default_import/Tickets/Submit and they might be able to assist better.

 

Curtains - Customize Windows with additional styles
Reply #3 from Stardock Forums Top

Yes, ..."the master can see the slave IP and cannot resolve the hostname"

 

Reply #4 from Stardock Forums Top

Perhaps I was unclear; do the secondaries have multiple network cards and thus, have multiple IP addresses (on the same PC? 

Reply #5 from Stardock Forums Top

My Master is a MS Surface 3.

ip:  192.168.1.114 

Only ethernet in use, WIFI off.

 

Slave is 192.168.117 and 192.168.1.118

I have set up a slave profile for both IP's on the master and admin' disabled the adapters to bring down to a single IP, no good :-(

2 x Ethernet ports.

Both active.

 

Subnet is 255.255.255.0

Gateway 192.168.1.1

 

Cheers

Bill

 

Reply #6 from Stardock Forums Top

Hi. Got an automated response from a 'bot at Stardock.... with a random selection of unrelated tutorials.

For what its worth I have tested by (a) disabling Norton 360 and (b) added a specific firewall exclusion between the 2 PC's - all ports, all traffic - no change.

ARP reports the mac addresses from both machines (and they match!)

Ping both ways - no probs. 

RDP works just fine.

etc etc etc.

 

 

 

Reply #7 from Stardock Forums Top

ok, deleted and re-installed everything - no change.

the master can 'see' the broadcasting slave and offers to add the machine based on the IP address, so it's doing half the job. 

password is correct. 

i dont know what else to try, support - well it's not supportive......

 

Reply #8 from Stardock Forums Top

SOLUTION:  Don't use IP addresses.  

Manually added the hostname, rebooted and it worked.  When asked "always connect using IP", say no - DO NOT USE THIS REDUNDANT FEATURE - IT DOESN'T WORK, or at best, is unstable.  The software clearly doesn't do reverse lookups.