Thanks, that worked perfectly.
James
>
> We're having trouble getting machine name resolution from an DNS server.
If
> we try to ping, for example, a machine named Mach1, we get an "unknown
host
> Mach1" error. If we ping the FQDN, Mach1.domainname.com, we get
resolut
On Wed, Sep 24, 2003 at 09:09:58AM -0700, James D. Parra wrote:
> Hello,
>
> We're having trouble getting machine name resolution from an DNS server. If
> we try to ping, for example, a machine named Mach1, we get an "unknown host
> Mach1" error. If we ping the FQDN
On Wed, 24 Sep 2003 09:09:58 -0700
"James D. Parra" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> We're having trouble getting machine name resolution from an DNS server.
> If
> we try to ping, for example, a machine named Mach1, we get an "unknown
> hos
Hello,
We're having trouble getting machine name resolution from an DNS server. If
we try to ping, for example, a machine named Mach1, we get an "unknown host
Mach1" error. If we ping the FQDN, Mach1.domainname.com, we get resolution.
Oddly, windows boxes can resolve the machine n
On 11-Jun-2003/14:04 +0100, "Hill, Benjamin W" <[EMAIL PROTECTED]> wrote:
>I have a Linux box that I'd like people to be able to access via it's
>machine name. However, to do this I have to add the IP address of the
>machine to the "hosts" file on a Windows machine. I guess this is something
>to do
I have a Linux box that I'd like people to be able to access via it's
machine name. However, to do this I have to add the IP address of the
machine to the "hosts" file on a Windows machine. I guess this is something
to do with WINS, or DNS servers...
Is there any way to allow Windows machines to c
