No DNS in Windows 2000 client

[john]

Archived from groups: microsoft.public.win2000.dns (More info?)

I have an old CPU with 2 NICs running Windows 98 and Sygate to share
my cable internet connection. This system has been running fine for 2
years with Windows 98 clients. Now I just bought a new client CPU and
installed Windows 2000 Professional on it - this connects to internet
and pings just fine, but does not see a DNS.
To be sure there was nothing wrong with the new client, I connected it
to a friend's DHCP router and it connected immediately to internet
with DNS and all.
So my question is: should I change any Windows 2000 network settings
in some way in order to get a DNS on my own system.
On my friend's network, ipconfig shows "connection-specific DNS
suffix" as: "lan", but on my own network, there is no entry there at
all.
Any pointers would be most welcome.
John

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:d017cdcb.0410080914.40718cc2@posting.google.com,
John <visitme@soon.com> commented
Then Kevin replied below:
> I have an old CPU with 2 NICs running Windows 98 and
> Sygate to share my cable internet connection. This system
> has been running fine for 2 years with Windows 98
> clients. Now I just bought a new client CPU and installed
> Windows 2000 Professional on it - this connects to
> internet and pings just fine, but does not see a DNS.
> To be sure there was nothing wrong with the new client, I
> connected it to a friend's DHCP router and it connected
> immediately to internet with DNS and all.
> So my question is: should I change any Windows 2000
> network settings in some way in order to get a DNS on my
> own system.
> On my friend's network, ipconfig shows
> "connection-specific DNS suffix" as: "lan", but on my own
> network, there is no entry there at all.
> Any pointers would be most welcome.
> John

The connection specific suffix can be either manually entered or supplied by
DHCP option 015. The lack of a connection suffix will not cause DNS to fail.
If you client is not getting DNS assigned then it is likely that the DHCP
server is not assigning one. Try manually configuring 4.2.2.1 and 4.2.2.2

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

[john]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message news:<#raSw1hrEHA.2776@TK2MSFTNGP14.phx.gbl>...
> In news:d017cdcb.0410080914.40718cc2@posting.google.com,
> John <visitme@soon.com> commented
> Then Kevin replied below:
> > I have an old CPU with 2 NICs running Windows 98 and
> > Sygate to share my cable internet connection. This system
> > has been running fine for 2 years with Windows 98
> > clients. Now I just bought a new client CPU and installed
> > Windows 2000 Professional on it - this connects to
> > internet and pings just fine, but does not see a DNS.
> > To be sure there was nothing wrong with the new client, I
> > connected it to a friend's DHCP router and it connected
> > immediately to internet with DNS and all.
> > So my question is: should I change any Windows 2000
> > network settings in some way in order to get a DNS on my
> > own system.
> > On my friend's network, ipconfig shows
> > "connection-specific DNS suffix" as: "lan", but on my own
> > network, there is no entry there at all.
> > Any pointers would be most welcome.
> > John
>
> The connection specific suffix can be either manually entered or supplied by
> DHCP option 015. The lack of a connection suffix will not cause DNS to fail.
> If you client is not getting DNS assigned then it is likely that the DHCP
> server is not assigning one. Try manually configuring 4.2.2.1 and 4.2.2.2
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
Hi Kevin,
Thanks for your assistance - I'll try your solution this week when I
have some time available and let you know whether it works. I assume
you mean 4.2.2.1 and 4.2.2.2 as primary and secondary DNS? Can you
explain to me why this should be an option - for future reference it'd
be nice to know a bit more about this subject!
Regards,
John

 

[john]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message news:<#raSw1hrEHA.2776@TK2MSFTNGP14.phx.gbl>...
> In news:d017cdcb.0410080914.40718cc2@posting.google.com,
> John <visitme@soon.com> commented
> Then Kevin replied below:
> > I have an old CPU with 2 NICs running Windows 98 and
> > Sygate to share my cable internet connection. This system
> > has been running fine for 2 years with Windows 98
> > clients. Now I just bought a new client CPU and installed
> > Windows 2000 Professional on it - this connects to
> > internet and pings just fine, but does not see a DNS.
> > To be sure there was nothing wrong with the new client, I
> > connected it to a friend's DHCP router and it connected
> > immediately to internet with DNS and all.
> > So my question is: should I change any Windows 2000
> > network settings in some way in order to get a DNS on my
> > own system.
> > On my friend's network, ipconfig shows
> > "connection-specific DNS suffix" as: "lan", but on my own
> > network, there is no entry there at all.
> > Any pointers would be most welcome.
> > John
>
> The connection specific suffix can be either manually entered or supplied by
> DHCP option 015. The lack of a connection suffix will not cause DNS to fail.
> If you client is not getting DNS assigned then it is likely that the DHCP
> server is not assigning one. Try manually configuring 4.2.2.1 and 4.2.2.2
>
> --
> Best regards,

Kevin,
Just one more question to satisfy my thirst for knowledge and
enlightenment. Is there something specific about the Windows 2000
dynamic IP network setup which causes loss of DNA through a software
NAT router, which doesn't occur with a default Windows 98 setting?
Thanks again,
John

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:d017cdcb.0410100436.2a00e103@posting.google.com,
John <visitme@soon.com> commented
Then Kevin replied below:

> Hi Kevin,
> Thanks for your assistance - I'll try your solution this
> week when I
> have some time available and let you know whether it
> works. I assume
> you mean 4.2.2.1 and 4.2.2.2 as primary and secondary
> DNS? Can you
> explain to me why this should be an option - for future
> reference it'd
> be nice to know a bit more about this subject!

You don't mention Active Directory or if you have an internal DNS. You only
mention you're not getting DNS addresses assigned, and your post leaves it
unclear if you know what DNS address is supposed to be assigned.
With all due respect, if this is not the case please post a better
description of your set up and what you expect it to be. I only suggest
those DNS address because they have be verified to be high-speed recursive
DNS servers. BTW, the term is Preferred and Alternate, primary and secondary
are zone types.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:d017cdcb.0410100934.1ed1bc23@posting.google.com,
John <visitme@soon.com> commented
Then Kevin replied below:
> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US>
> wrote in message
> news:<#raSw1hrEHA.2776@TK2MSFTNGP14.phx.gbl>...
>> In news:d017cdcb.0410080914.40718cc2@posting.google.com,
>> John <visitme@soon.com> commented
>> Then Kevin replied below:
>>> I have an old CPU with 2 NICs running Windows 98 and
>>> Sygate to share my cable internet connection. This
>>> system has been running fine for 2 years with Windows 98
>>> clients. Now I just bought a new client CPU and
>>> installed Windows 2000 Professional on it - this
>>> connects to internet and pings just fine, but does not
>>> see a DNS.
>>> To be sure there was nothing wrong with the new client,
>>> I connected it to a friend's DHCP router and it
>>> connected immediately to internet with DNS and all.
>>> So my question is: should I change any Windows 2000
>>> network settings in some way in order to get a DNS on my
>>> own system.
>>> On my friend's network, ipconfig shows
>>> "connection-specific DNS suffix" as: "lan", but on my
>>> own network, there is no entry there at all.
>>> Any pointers would be most welcome.
>>> John
>>
>> The connection specific suffix can be either manually
>> entered or supplied by DHCP option 015. The lack of a
>> connection suffix will not cause DNS to fail. If you
>> client is not getting DNS assigned then it is likely
>> that the DHCP server is not assigning one. Try manually
>> configuring 4.2.2.1 and 4.2.2.2
>>
>> --
>> Best regards,
>
> Kevin,
> Just one more question to satisfy my thirst for knowledge
> and
> enlightenment. Is there something specific about the
> Windows 2000
> dynamic IP network setup which causes loss of DNA through
> a software
> NAT router, which doesn't occur with a default Windows 98
> setting?

OK, you have successfully confused me with this question.
Win98 does not support dynamic DNS registration as Win2k and later OS's do.
If you configure Win2k to register in DNS, it will attempt to register PTR
records in the authoritative reverse DNS for its IP address and
authoritative forward lookup for the domain name in the primary or
connection specific DNS suffix setting.
If Win98 needs its addresses registered in DNS, DHCP servers that support
this will have to do it.



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:e1QPjovrEHA.3464@TK2MSFTNGP14.phx.gbl,
Kevin D. Goodknecht Sr. [MVP] <admin@nospam.WFTX.US> made a post then I
commented below
>
> OK, you have successfully confused me with this question.
> Win98 does not support dynamic DNS registration as Win2k and later
> OS's do. If you configure Win2k to register in DNS, it will attempt
> to register PTR records in the authoritative reverse DNS for its IP
> address and authoritative forward lookup for the domain name in the
> primary or connection specific DNS suffix setting.
> If Win98 needs its addresses registered in DNS, DHCP servers that
> support this will have to do it.

Kevin, I don;t think he has AD, just a simple network at home, previously
using Win98 and sybase to share out a connection.

I think the win2k machine is not picking up an IP from the sygate box,
unless I misunderstood.

John, when you have the win2k machine connected to your network, run an
ipconfig /all and find out exactly what you are getting. If you can post
that, that would be great!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================