no name resolution on the Win95 client

no name resolution on the Win95 client

Post by Ben Hampso » Tue, 06 Oct 1998 04:00:00



I have a Linux Red Hat 5.1 server and a couple Win95 clients.  The server is
running named, dhcpd, smbd, nmbd.  When I log on with a Win95 client, I get
an IP address, can see the samba shares and can telnet to the Linux server.
But, during log on I get a warning that no DNS server is found, some
services may not be available.  This warning is true, I get no name
resolution on the Win95 client.  The Linux server has name resolution. How
do I make the Win95 client not error on login and get name resolution?

any clues, Ben.

 
 
 

no name resolution on the Win95 client

Post by Tobias Reckha » Thu, 08 Oct 1998 04:00:00


This is the most obvious, of course, but have you specified the Linux
box's IP address as a DNS server in Win95's TCP/IP properties? It
works on my systems (Linux gateway/server running named, smbd, nmbd,
no dhcpd yet).

Tobias



Quote:>I have a Linux Red Hat 5.1 server and a couple Win95 clients.  The server is
>running named, dhcpd, smbd, nmbd.  When I log on with a Win95 client, I get
>an IP address, can see the samba shares and can telnet to the Linux server.
>But, during log on I get a warning that no DNS server is found, some
>services may not be available.  This warning is true, I get no name
>resolution on the Win95 client.  The Linux server has name resolution. How
>do I make the Win95 client not error on login and get name resolution?

>any clues, Ben.

--


 
 
 

no name resolution on the Win95 client

Post by Ben Hampso » Thu, 08 Oct 1998 04:00:00


Yes, I have, but do you the log on to the NT server checked also?


>This is the most obvious, of course, but have you specified the Linux
>box's IP address as a DNS server in Win95's TCP/IP properties? It
>works on my systems (Linux gateway/server running named, smbd, nmbd,
>no dhcpd yet).

>Tobias



>--
>Tobias Reckhard (jester)


 
 
 

no name resolution on the Win95 client

Post by John Arrowwoo » Fri, 09 Oct 1998 04:00:00



> I have a Linux Red Hat 5.1 server and a couple Win95 clients.  The server is
> running named, dhcpd, smbd, nmbd.  When I log on with a Win95 client, I get
> an IP address, can see the samba shares and can telnet to the Linux server.
> But, during log on I get a warning that no DNS server is found, some
> services may not be available.  This warning is true, I get no name
> resolution on the Win95 client.  The Linux server has name resolution. How
> do I make the Win95 client not error on login and get name resolution?

> any clues, Ben.

This should be obvious, but on the Win95 box, run winipcfg and see what it
says your DNS server is.  Chances are, it's not specified.  Because you
are running DHCP, you obviously don't want to muck with putting the DNS in
the TCP/IP properties on the windows box.

I'm guessing that the DHCP server is not reporting the correct IP address
for the DNS server.  Alternatively, could the DNS server have died?  Or
is it set up properly to resolve intra-net addresses?  Any of these
*MIGHT* be a reason for Win95 to complain.

 
 
 

no name resolution on the Win95 client

Post by Tobias Reckha » Fri, 09 Oct 1998 04:00:00


I wouldn't know why, but then again, I don't use DHCP (which I still
think is the problem - DNS and DHCP not getting along, since you need
some form of dynamic DNS in a DHCP environment). I'm guessing that
logging on to an NT server merely moves password checking from the
individual desktop box to the NT server, but since I don't have an NT
server, I can't be sure.



>Yes, I have, but do you the log on to the NT server checked also?


>>This is the most obvious, of course, but have you specified the Linux
>>box's IP address as a DNS server in Win95's TCP/IP properties? It
>>works on my systems (Linux gateway/server running named, smbd, nmbd,
>>no dhcpd yet).

>>Tobias



>>--
>>Tobias Reckhard (jester)


--

 
 
 

no name resolution on the Win95 client

Post by Tobias Reckha » Sat, 10 Oct 1998 04:00:00


John is making sense, I think I've been misled - probably the Win95
can't even contact the DNS server.. Have you triple-checked your DHCP
configuration? And the DNS setup? Are you certain that the Linux box
is using its DNS server to perform name resolution? Or are you maybe
blocking ports with ipfwadm? That happened to me when my PPP link was
up - I didn't notice for a while, though, because named was querying
my ISPs servers when it couldn't contact itself..

Tobias




>> I have a Linux Red Hat 5.1 server and a couple Win95 clients.  The server is
>> running named, dhcpd, smbd, nmbd.  When I log on with a Win95 client, I get
>> an IP address, can see the samba shares and can telnet to the Linux server.
>> But, during log on I get a warning that no DNS server is found, some
>> services may not be available.  This warning is true, I get no name
>> resolution on the Win95 client.  The Linux server has name resolution. How
>> do I make the Win95 client not error on login and get name resolution?

>> any clues, Ben.

>This should be obvious, but on the Win95 box, run winipcfg and see what it
>says your DNS server is.  Chances are, it's not specified.  Because you
>are running DHCP, you obviously don't want to muck with putting the DNS in
>the TCP/IP properties on the windows box.

>I'm guessing that the DHCP server is not reporting the correct IP address
>for the DNS server.  Alternatively, could the DNS server have died?  Or
>is it set up properly to resolve intra-net addresses?  Any of these
>*MIGHT* be a reason for Win95 to complain.

--

 
 
 

1. no name resolution on the Win95 client

I have a Linux Red Hat 5.1 server and a couple Win95 clients.  The server is
running named, dhcpd, smbd, nmbd.  When I log on with a Win95 client, I get
an IP address, can see the samba shares and can telnet to the Linux server.
But, during log on I get a warning that no DNS server is found, some
services may not be available.  This warning is true, I get no name
resolution on the Win95 client.  The Linux server has name resolution. How
do I make the Win95 client not error on login and get name resolution?

any clues, Ben.

2. apache_1.3.27 / mod_ssl-2.8.12-1.3.27

3. dhcp client and dns name resolution

4. problems booting

5. Linux Client Name Resolution via CIFS Server

6. LILO dual boot eats hard drive: Film at 11! :)

7. Name resolution problems on windows client

8. Xwin configuration problem on Solaris 2.5.1

9. BIND Name resolution & the NAMED.CA file

10. Help: Very slow name resolution on AIX 4.3.2 with name server

11. BIND Name resolution & the NAMED.CA file (and an apology)

12. Name resolution for local names using DHCP

13. named and name resolution