DNS problem local network with wireless router

  • Thread starter Thread starter sb
  • Start date Start date
S

sb

hi,
I have a small home network with one Windows 2000 AD server and one other
Windows 2000 server. Everything was working perfectly. I installed a
wireless router to enable my new laptop to access the Internet and my
network. Since doing this, any computer going through this new router
cannot access network Resources by name, only IP address. Addresses for
external web sites are resolved properly.
Any ideas?
 
In
sb said:
hi,
I have a small home network with one Windows 2000 AD server and one
other Windows 2000 server. Everything was working perfectly. I
installed a wireless router to enable my new laptop to access the
Internet and my network. Since doing this, any computer going
through this new router cannot access network Resources by name, only
IP address. Addresses for external web sites are resolved properly.
Any ideas?
Click to expand...

We'll need more info to go on. Let's start with:

1. An unedited iconfig /all of the DC, the server and the latpop.
2. What is supplying DHCP services?
3. Are your machines using your ISP's DNS or only your internal AD DNS? If
using the ISP's, I can see why you are having internal resolution problems.
This will also cause major issues with AD.

--
Ace

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

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Microsot Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
Thanks for the reply. Part of the fun has been getting my laptop from work
(which has its own domain) to work on my domain at home.

I am using the AD server as the local DNS Server and added my DSL Router
(192.168.1.254) and my ISP's DNS's (205.152.53.252 and 205.152.37.254) as
alternates.

DSL Router has DHCP and provides address to w2k AD server's 3Com NIC.

w2k AD server has DHCP provides addresses to other computers and WAN
connection of wireless router.

Wireless router has DHCP and provides addresses to wireless clients and up
to 4 wired workstations.

I have a diagram but Microsoft does not allow attachments

Any ideas appreciated,



-----------------------


W2k AD server


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : NT2K
Primary DNS Suffix . . . . . . . : Winnt2k.local
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Winnt2k.local
launchmodem.com

Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21143 Based PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-C0-F0-4D-10-74

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.16.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.16.1
205.152.53.252
205.152.37.254
192.168.1.254

Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : launchmodem.com
Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI TX NIC
(3C905B-TX) #2
Physical Address. . . . . . . . . : 00-10-5A-E1-88-E4

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Wednesday, September 28, 2005 3:36:07 PM

Lease Expires . . . . . . . . . . : Thursday, September 29, 2005 3:36:07 PM


---------------------------
W2k pro connected through wireless router

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : oemcomputer
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-40-45-00-27-92

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Tuesday, September 27, 2005 2:31:03 PM

Lease Expires . . . . . . . . . . : Tuesday, October 04, 2005 2:31:03 PM

----------------------------
WXP pro wirless laptop


Windows IP Configuration

Host Name . . . . . . . . . . . . : LRS-ALB-JJ7KQ71

Primary Dns Suffix . . . . . . . : corp.dl.private.dl

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : corp.dl.private.dl

dl.private.dl

private.dl

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Dell Wireless 1350 WLAN Mini-PCI
Card

Physical Address. . . . . . . . . : 00-0B-7D-26-22-22

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Thursday, September 29, 2005
9:17:40 AM

Lease Expires . . . . . . . . . . : Thursday, October 06, 2005
9:17:40 AM



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Controller

Physical Address. . . . . . . . . : 00-12-3F-D2-4A-85
 
In
swb317 said:
Thanks for the reply.
Click to expand...

Thanks for posting your configuration information. Please read my comments
below...
Part of the fun has been getting my laptop
from work (which has its own domain) to work on my domain at home.
Click to expand...

That is a tough one without disjoining it from the corp domain and joining
your home domain, then when you take it to work, disjoin it from your home
domain and re-join it back to your corporate domain. If the laptop is now
yours, you can disjoing corp, and join your home domain permanently.

I am using the AD server as the local DNS Server and added my DSL
Router (192.168.1.254) and my ISP's DNS's (205.152.53.252 and
205.152.37.254) as alternates.
Click to expand...

Actually you shouldn't do that. With AD, all machines that are part of the
domain (DCs and clients) must only use the DNS server that is hosting the AD
zone. This is because your router or ISP does not host the zone, therefore
they do not know "where" your AD services are located.

Whe your client logs on, or the DC needs to locate a specific service in AD,
it queries DNS. Your router or ISP do not have that answer. This is a common
misconfiguration and causes numerous headaches. This is why you can't
resolve names internally. If a client queries an outside name, your DNS will
find it for you with the Root Hints. You can increase outside resolution
efficiency by configuring a forwarder. If this is Windows 2000, see link
below on how to configure a forwarder to your ISP's DNS server.
http://support.microsoft.com/?id=300202

DSL Router has DHCP and provides address to w2k AD server's 3Com NIC.

w2k AD server has DHCP provides addresses to other computers and WAN
connection of wireless router.
Click to expand...

You mean the DC has two NICs? Not usually suggested and causes additional
issues. There are multiple steps including registry changes to insure proper
AD functionality for the DC and clients. Usually we recommend to use a
member server for a router or NAT, but even better to just let your
DSL/Cable router handle NAT, and only NAT (other than if it has a firewall).
We suggest not to use a DSL/Router as the DNS address, nor as a DHCP server,
because Microsoft's DHCP supports additional functionality and Options that
routers don't support, such as Dynamic DNS Updates (DHCP Scope or Global
Option 081).

Wireless router has DHCP and provides addresses to wireless clients
and up to 4 wired workstations.
Click to expand...

As mentioned, I would suggest to use the DC's DHCP service and not the
router's for all your internal client machines. You can even set the
wireless router (if not the same as your DSL router), for DHCP pass through
from your wired network, the Microsoft DHCP service running on the domain
controller. This means setting the wireless router in "corporate" mode,
which will "bridge" the wireless and wired network on the same IP subnet so
it will not need to do any routing, which can complicate matters a bit. The
"corporate mode" terminology may be different on different routers based on
the wireless router manufacturer. They may simply call it "bridge" mode.

More comments on your configuration....

I have a diagram but Microsoft does not allow attachments.
Click to expand...

******Email it to me please.

Any ideas appreciated,



-----------------------


W2k AD server


Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : NT2K
Primary DNS Suffix . . . . . . . : Winnt2k.local
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Winnt2k.local
launchmodem.com

Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21143 Based PCI Fast
Ethernet Adapter
Physical Address. . . . . . . . . : 00-C0-F0-4D-10-74

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.16.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.16.1
205.152.53.252
205.152.37.254
192.168.1.254
Click to expand...

******Use only 192.168.16.1 for DNS. This is one major cause of your
dilemma.

Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : launchmodem.com
Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI TX NIC
(3C905B-TX) #2
Physical Address. . . . . . . . . : 00-10-5A-E1-88-E4

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254
Click to expand...

******Make sure that DNS address is hardcoded to 192.168.16.1 (the DC
itself). Don't use any other DNS please.

Lease Obtained. . . . . . . . . . : Wednesday, September 28, 2005
3:36:07 PM

Lease Expires . . . . . . . . . . : Thursday, September 29, 2005
3:36:07 PM






---------------------------
W2k pro connected through wireless router

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : oemcomputer
Primary DNS Suffix . . . . . . . :
Click to expand...


******This machine has no Primary DNS Suffix. Is this machine an AD member
(joined to a domain)?


Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-40-45-00-27-92

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1
Click to expand...

******This should be the AD DC's DNS server only, 192.168.16.1. Setup
Microsoft's DHCP and set option 006 to only 192.168.16.1.


Lease Obtained. . . . . . . . . . : Tuesday, September 27, 2005
2:31:03 PM

Lease Expires . . . . . . . . . . : Tuesday, October 04, 2005 2:31:03
PM

----------------------------
WXP pro wirless laptop


Windows IP Configuration

Host Name . . . . . . . . . . . . : LRS-ALB-JJ7KQ71

Primary Dns Suffix . . . . . . . : corp.dl.private.dl
Click to expand...

******Is this machine joined to the corp domain? Primary DNS Suffix points
to that, and indicative of a machines joined to a domain.

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : corp.dl.private.dl

dl.private.dl

private.dl

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Dell Wireless 1350 WLAN
Mini-PCI Card

Physical Address. . . . . . . . . : 00-0B-7D-26-22-22

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1
Click to expand...


******This should be the AD DC's DNS server only, 192.168.16.1. As I
suggested, setup Microsoft's DHCP and set option 006 to only use
192.168.16.1.

Lease Obtained. . . . . . . . . . : Thursday, September 29,
2005 9:17:40 AM

Lease Expires . . . . . . . . . . : Thursday, October 06, 2005
9:17:40 AM



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller

Physical Address. . . . . . . . . : 00-12-3F-D2-4A-85
Click to expand...

I hope that helps,
Ace
 
Back
Top