Problem with TightVNC?
Problem with TightVNC?
I think Microsoft has made something very silly here. If you want a hack that just makes it work, you can put an entry in the HOSTS file on the remote machine (not the server) to map to your local LAN IP. I usually use the IP address because of all these strange issues. Your problem is likely related to having a Microsoft machine name when it should be using a DNS-based name instead. These names are somewhat connected but it gets very confusing at times when Microsoft decides on its own what the name is. It could also be browser-related since tightvnc clients usually run from inside a web browser. There are so many different browser settings and junk data being saved that it's hard to tell exactly which one something uses. If you can ping the server using its name instead of the IP address, does it consistently respond? That would suggest there was an issue with the browser. Again, this is why I always use IP addresses
Bill, thanks so much for the info! Sorry if this got stuck in my inbox for a while; things happen all the time. I'm totally fine with using the IP address, but there are several local machines on the network and some users get mixed up without knowing who they're talking to. No big deal, the problem went away overnight. Honestly, I rebooted everything many times before even posting here, so it just seems like another weird thing that Windows does. Hmm... where is the "Best Answer" button?
All over to the far right. Put a checkmark next to it, but draw a round dot in the middle of that symbol.