Hi there,

I THINK I may have discovered a bug in BOINC. It seems to be new, but may not be.

When I create my "remote_hosts.cfg" file on a Windows Vista host, I add my hostname, which is "mobrien24-1". However, I get the message "Can't resolve hostname mobrien24-1 in remote_hosts.cfg" when I try to access it from this machine. However, if I add the machine's IP address, it works just fine. I wonder if it has a problem with the "minus sign"/"dash" in the hostname.

Any other host listed in the file works fine. It would be nice to not have to update this file every time my RPC client's IP changes. (Fortunately, my router tends to assign the same one to this machine, so it is rare that it changes). Also, this issue doesn't seem to occur on Linux BOINC hosts, 32 or 64 bit. They can parse this machine name just fine.

Please let me know if I can be of any more help, or if I'm on the wrong track or forgetting something.

--mobrien118

Forwarded to the developers.

---

For clarification, is this a remote machine you are trying to reach, or is this the machine you're working from?

Can you ping the machine from a command line window?
Do you know what your network is based on, NetBIOS or DNS?

If it's the machine you're working from, try adding "localhost" (without quotes) instead of its name.

---

Sorry I don't know which directory it's in.

Wasn't that /etc/hosts?

Sorry I don't know which directory it's in.

Wasn't that /etc/hosts?

It's /etc/hosts on Linux but the OP is using Vista.

It's "C:\Windows\System32\drivers\etc" on Vista32 (and that sounds very familiar from other NT-based Windows versions, too)