Determining FQDN for Workgroup Machine

  • Thread starter Thread starter Chris Holiman
  • Start date Start date
C

Chris Holiman

I have an application that attempts to use the machine's FQDN to talk
to a service running on the same machine. The application reports
that it cannot locate the machine.

According the application's manufacturer, the issue is that, when
using DNS for name resolution, the app cannot connect and a hosts file
should be used. The problem is that the computer is not in any
domain, but is in a workgroup (called, quite originally, workgroup).
I've tried a variety of entries in the hosts file, but none seem to
work.

In short, can anyone tell me how to correctly represent the FQDN of a
workgroup computer? Alternately, maybe this really isn't the problem
and someone has a better idea.

Thanks in advance,

Chris
 
What's dishing out DHCP addresses? Can you add a DNS suffix, even a fake
one? computer.bogus.com ?
 
DHCP comes from an SMC cable router. I tried the suffix, but it
didn't help. The issue may be caused by something else, but I wish I
knew what the app was looking for.
 
OK - so if you put

xxx.xxx.xxx.xxx OtherComputername

in the hosts file on the computer running this app, can you ping
OtherComputername? The computer should look at hosts before it tries DNS
resolution....

Chris said:
DHCP comes from an SMC cable router. I tried the suffix, but it
didn't help. The issue may be caused by something else, but I wish I
knew what the app was looking for.

"Lanwench [MVP - Exchange]"
What's dishing out DHCP addresses? Can you add a DNS suffix, even a
fake one? computer.bogus.com ?
Click to expand...
Click to expand...
 
Back
Top