DNS problem (ADSL)

[Peter]

Hi,

After weeks struggling with this problem and consulting some dutch
newsgroups maybe here someone can help.

Setup:
- Modem/router Allied Data Copperjet 810
- Router US-Robotics
- 1 pc with Win 95
- 2 pc's with Win XP
- 1 dualboot pc with Win 2000 and Linux (SuSE)

Browsing the internet works on all except under Win 2000. Pinging from this
pc to an ip-adress works fine, but pinging to a name (ie GOOGLE.COM) gives
"unknown host". But then pinging an other pc in the network by ip-adress AND
by name works fine.

All pc's have setting "Automatic ip-adress" and "Automatic DNS-server".
Output of command ipconfig /all gives on XP-pc's and W95 pc's (with
winipcfg) nicely an ip-adress given bij the US-Robotics router. Only the
W2000 pc gives a very strange ip-adress wich even isn't in the range of
ip-adresses from the USR-router.

I have allready searched Microsofts Knowledge base. There is a huge lot of
information there but everything I tried didn't help.

Can somebody please point me in the right direction to resolve this problem.
(I don't want to re-install Windows.)

Thanks,
Peter

 

[Herb Martin]

Hi,

After weeks struggling with this problem and consulting some dutch
newsgroups maybe here someone can help.

Probably because most of the detail given below is irrelevant to a DNS
problem.

Browsing the internet works on all except under Win 2000. Pinging from this
pc to an ip-adress works fine, but pinging to a name (ie GOOGLE.COM) gives
"unknown host". But then pinging an other pc in the network by ip-adress AND
by name works fine.

So you have a name resolution problem.

EITHER:
The PCs are set to the wrong DNS server addresses
The DNS server they use is setup incorrectly
Or there is a firewall between that is preventing the DNS lookups from
completing

All pc's have setting "Automatic ip-adress" and "Automatic DNS-server".

And what setting do they receive? Automatic or not automatic is irrelevant
but the ACTUAL DNS server is the KEY.

Output of command ipconfig /all gives on XP-pc's and W95 pc's (with
winipcfg) nicely an ip-adress given bij the US-Robotics router. Only the
W2000 pc gives a very strange ip-adress wich even isn't in the range of
ip-adresses from the USR-router.

Then change it. If you have a domain internally the above is wrong even if
it does work for the Internet.

I have allready searched Microsofts Knowledge base. There is a huge lot of
information there but everything I tried didn't help.

Does the router FORWARD or perform direct RECURSION from the Internet
root down? (Do you have the router configured to send requests to an ISP
DNS
server?)

IF you have an internal Domain it should work this way:

ALL internal clients set to the INTERNAL DNS server
Internal clients include the internal DNS server itself and any DCs or
other servers
NO outside DNS server nor the router should be listed (usually)
The internal DNS server should then FORWARD to the Router (or to the
ISP)

The router should EITHER forward to the ISP or use the actual Internet root
servers
to do direct recursion of the Internet namespace

Optionally, if you have no internal Win2000+ domain:
Point all clients to the router, have it forward or recurse the Internet
namespace.


\> Setup:

 

[Ace Fekay [MVP]]

In

Hi,

After weeks struggling with this problem and consulting some dutch
newsgroups maybe here someone can help.

Setup:
- Modem/router Allied Data Copperjet 810
- Router US-Robotics
- 1 pc with Win 95
- 2 pc's with Win XP
- 1 dualboot pc with Win 2000 and Linux (SuSE)

Browsing the internet works on all except under Win 2000. Pinging
from this pc to an ip-adress works fine, but pinging to a name (ie
GOOGLE.COM) gives "unknown host". But then pinging an other pc in the
network by ip-adress AND by name works fine.

All pc's have setting "Automatic ip-adress" and "Automatic
DNS-server". Output of command ipconfig /all gives on XP-pc's and W95
pc's (with winipcfg) nicely an ip-adress given bij the US-Robotics
router. Only the W2000 pc gives a very strange ip-adress wich even
isn't in the range of ip-adresses from the USR-router.

I have allready searched Microsofts Knowledge base. There is a huge
lot of information there but everything I tried didn't help.

Can somebody please point me in the right direction to resolve this
problem. (I don't want to re-install Windows.)

Thanks,
Peter

Wow, this got double posted somehow. But in addition to the other responses,

1. I would like to see, as Kevin in the other thread requested, an ipconfig
/all of the W2k box and of one of the boxes that is working.

2. I have a feeling that the IP on the machine that is not working is
169.254.x.x.

3. If #2 is correct, I have a feeling that it might be a bad wire, incorrect
NIC driver or a faulty NIC.

But we should still see #1 please to confirm and better help.


On a side note, if you have AD, I would never use the Router for a DHCP
server. It does not support DHCP Option 081 and it does not work hand in
hand with MS DNS API services, which allows for dynamic registration of your
DHCP clients (mainly legacy clients). It's more of a recommendation and not
a "MUST DO", but most engineers in these newsgroups will agree. Use MS DHCP
services.

Also, another side if you are using AD, I hope that you only are using your
MS DNS server IP addresses in your machines' properties (THIS means all
machines, DCs and clients). Please do not use an ISP's DNS server or the
router as a DNS address in your machines or many other things WILL occur.
This is a MUST AND a recommendation if using AD.

If not running AD, disregard the two previous paragraphs.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Peter]

"Ace Fekay [MVP]"

In

Wow, this got double posted somehow. But in addition to the other responses,

1. I would like to see, as Kevin in the other thread requested, an ipconfig
/all of the W2k box and of one of the boxes that is working.

Here's the one from the Win2k (the "faulty" one):
C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : roro-pc
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810X Family PCI
Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-10-A7-14-AC-37
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.178.189
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :


And here's the one from a XP pc:

D:\>ipconfig /all

Windows IP-configuratie

Host-naam . . . . . . . . . . . .: isl-pc
Primair DNS-achtervoegsel. . . . .:
Knooppunttype: . . . . . . . . . .: onbekend
IP-routering ingeschakeld. . . . .: nee
WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter Draadloze netwerkverbinding:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving . . . . . . . . . . .:
U.S. Robotics 802.11g Wireless Turbo Adapter
Fysiek adres. . . . . . . . . . . : 00-C0-49-CC-4A-FB
DHCP ingeshakeld. . . . . . . . . : ja
Autom. configuratie ingeschakeld. : ja
IP-adres. . . . . . . . . . . . . : 192.168.123.102
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 192.168.123.254
DHCP-server . . . . . . . . . . . : 192.168.123.254
DNS-servers . . . . . . . . . . . : 192.168.123.254
Lease verkregen . . . . . . . . . : zaterdag 3 januari 2004 11:30:09
Lease verlopen . . . . . . . . . : zaterdag 10 januari 2004
11:30:09

Ethernet-adapter LAN-verbinding:

Status van medium . . . . . . . . : medium ontkoppeld
Beschrijving . . . . . . . . . . .:
Realtek RTL8139 Family PCI Fast Ethernet NIC
Fysiek adres. . . . . . . . . . . : 00-10-A7-14-AF-70


At this moment it works via a wireless lan configuration. It also worked via
a normal NIC (see last for lines here above).

2. I have a feeling that the IP on the machine that is not working is
169.254.x.x.

Yes! That's right!

3. If #2 is correct, I have a feeling that it might be a bad wire, incorrect
NIC driver or a faulty NIC.

I doubt that a little bit, why?
- I replaced the NIC several times (I have some spare ones),
- I installed the drivers several times,
- I removed all network related hardware and removed all drivers and cleaned
the registry a few times,
- I downloaded new drivers from the internet,
- etc.

But most strange of all... that pc is a dualboot system and under Linux the
NIC works perfectly.

Oh yes, something strange I noted. When replacing and reinstalling the NIC
several times it looked that if under hardware the number of the NIC was
higher every time. I.e.
- after first install: Realtek RTL8139/810X Family PCI Fast Ethernet NIC
- after sixt install/driver upgrade etc.: Realtek RTL8139/810X Family PCI
Fast Ethernet NIC #6

But we should still see #1 please to confirm and better help.


On a side note, if you have AD, I would never use the Router for a DHCP
server. It does not support DHCP Option 081 and it does not work hand in
hand with MS DNS API services, which allows for dynamic registration of your
DHCP clients (mainly legacy clients). It's more of a recommendation and not
a "MUST DO", but most engineers in these newsgroups will agree. Use MS DHCP
services.

Also, another side if you are using AD, I hope that you only are using your
MS DNS server IP addresses in your machines' properties (THIS means all
machines, DCs and clients). Please do not use an ISP's DNS server or the
router as a DNS address in your machines or many other things WILL occur.
This is a MUST AND a recommendation if using AD.

If not running AD, disregard the two previous paragraphs.

As far as I know I don't have AD. At least I never configured it or choose
it myself.

Peter

 

[Ace Fekay [MVP]]

In

"Ace Fekay [MVP]"


Here's the one from the Win2k (the "faulty" one):
C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : roro-pc
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810X
Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-10-A7-14-AC-37
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.178.189
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :


And here's the one from a XP pc:

D:\>ipconfig /all

Windows IP-configuratie

Host-naam . . . . . . . . . . . .: isl-pc
Primair DNS-achtervoegsel. . . . .:
Knooppunttype: . . . . . . . . . .: onbekend
IP-routering ingeschakeld. . . . .: nee
WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter Draadloze netwerkverbinding:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving . . . . . . . . . . .:
U.S. Robotics 802.11g Wireless Turbo Adapter
Fysiek adres. . . . . . . . . . . : 00-C0-49-CC-4A-FB
DHCP ingeshakeld. . . . . . . . . : ja
Autom. configuratie ingeschakeld. : ja
IP-adres. . . . . . . . . . . . . : 192.168.123.102
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 192.168.123.254
DHCP-server . . . . . . . . . . . : 192.168.123.254
DNS-servers . . . . . . . . . . . : 192.168.123.254
Lease verkregen . . . . . . . . . : zaterdag 3 januari 2004
11:30:09 Lease verlopen . . . . . . . . . : zaterdag 10
januari 2004 11:30:09

Ethernet-adapter LAN-verbinding:

Status van medium . . . . . . . . : medium ontkoppeld
Beschrijving . . . . . . . . . . .:
Realtek RTL8139 Family PCI Fast Ethernet NIC
Fysiek adres. . . . . . . . . . . : 00-10-A7-14-AF-70


At this moment it works via a wireless lan configuration. It also
worked via a normal NIC (see last for lines here above).



Yes! That's right!



I doubt that a little bit, why?
- I replaced the NIC several times (I have some spare ones),
- I installed the drivers several times,
- I removed all network related hardware and removed all drivers and
cleaned the registry a few times,
- I downloaded new drivers from the internet,
- etc.

But most strange of all... that pc is a dualboot system and under
Linux the NIC works perfectly.

Oh yes, something strange I noted. When replacing and reinstalling
the NIC several times it looked that if under hardware the number of
the NIC was higher every time. I.e.
- after first install: Realtek RTL8139/810X Family PCI Fast Ethernet
NIC
- after sixt install/driver upgrade etc.: Realtek RTL8139/810X Family
PCI Fast Ethernet NIC #6



As far as I know I don't have AD. At least I never configured it or
choose it myself.

Peter

I had a feeling the 169.254.x.x number showed up. That is the APIPA
(Automatic Private IP Address) which the system gives when it's configured
for an auto IP but either the DHCP server cannot be reached, driver problem
or wire problem.

So guessing at this time, sounds like so far it could be...

1. Driver problem
2. Certain Services may be disabled? Such as:
DHCP CLient Service'
MS Client Service (NIC properties)
File and Print Services (NIC properties)

As for the other NICs that show up in Add/Remove Hardware, remove the
physical NIC, then I would delete all of the drivers that show up (click to
show Hidden Devices as well), then restart. Then shut it down, install the
NIC, then boot and let it find the NIC and install the default drivers. I'm
assuming this since you said it works under Linux.

But curious, how do you have Linux setup as a dualboot? Are you using LiLo?
Have a feeling it may also have something to do with that? Not sure at this
time since I don't know enough about dualbooting it with Linux, but both
Operating Systems are system controlling and one of them wants to be the
primary system.

If all else fails, have you considered removing the NIC (removing all the
drivers and Devices as above), then re-running setup as an upgrade (it will
repair the installation without losing your settings). I realized you've
already cleaned and did many other things and drivers, etc, but just maybe a
reinstall/upgrade may help.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory