Re: Urgent - please help

"Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:766A8D9D-5749-47F5-B15D-28E2F3EA7CC3@xxxxxxxxxxxxxxxx
Here is the ipconfig /all info from the XP Pro client that cannot join the
domain.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Allan
Primary Dns Suffix . . . . . . . :

Go to System Control Panel->Computer Name and
add the computers domain as the primary suffix for
the machine.

Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP EN1207D-TX PCI 10/100 Fast
Ethern
et Adapter
Physical Address. . . . . . . . . : 00-10-B5-B8-0B-03
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DHCP Server . . . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.1

Correct based on your report below (the DNS-DC.)

Lease Obtained. . . . . . . . . . : 15 décembre, 2006 04:10:13
Lease Expires . . . . . . . . . . : 16 décembre, 2006 04:10:13

The routers ip address is 192.168.1.2 - the DC is 192.168.1.1. Given the
above, are we still looking at a misdirected DNS server, or is it
something
else? The only DNS address I put on the router is 192.168.1.1, to make
sure
that a client connecting to the router is directed back to the DC for DNS
resolution.

Ok (but that isn't the way I would do the last part.)

Instead, I would set the router to use the ISP or recurse
as DNS Server, and point the DC-DNS server to the
router as "Forwarder" (in DNS MMC Server properties.)

Since the client is ok, check the same stuff on the DC,
and run DCDiag -- capture output to a text file -- search
for WARN and FAIL -- fix or post results here.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Joe



"Herb Martin" wrote:

"myweb" <meiweb@xxxxxx> wrote in message
news:59710d1e1378c8ee76e58c8500@xxxxxxxxxxxxxxxxxxxxxxx
Hello Joe,

Did the router also provide the DNS server IP? Sounds that the DNS
settings causing the problem.


Agreeing with "myweb" and amplifying:

Many such routers as DHCP servers give out their OWN address
as the DNS server (some can be modified to set this, but others
cannot.)

The INTERNAL clients must use STRICTLY the INTERNAL
(and dynamic) DNS Server which supports AD -- you indicate
this is the DC.

"ipconfig /all" and look for either the wrong OR a mixture of
DNS servers (DC and router would be wrong too.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.



Thanks for the quick response.

The IP for the DC is fixed. All workstations use DHCP. DHCP server is
the router. Not sure what the "DG" is.

All PC's connect to a switch, which connects to the router. Also the
DC has only one NIC, which connects to the switch. The ISP DSL modem
is connected directly to the router. Hope this is clear. To put it
another way, there are two connections to the router, one from the
switch, the other from the modem.

Joe

"myweb" wrote:

Hello Joe,

Did you use fixed IP? DHCP from the router or server, are the
settings ok with the DG? How is the connection runnning, all over the
router or did you use a switch?

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
Customer has SBS 2003 with 7 workstations. After replacing the
router to which all workstations connect, workstations no longer log
in to the AD domain, and cannot join the AD domain. For DNS, I have
verified that all workstations and the DC point to the DC, which is
also a DNS server, for DNS resolution.

When I use netdom join to join an XP Pro workstation to the domain,
I get a "network path not found" message. When I look at Network
Neighbourhood, the domain is there but if I try to open it, it tells
me (I can't remember the exact wording) that the either the domain
cannot be found or I do not have permission.

I can ping the DC from the XP workstation, and I can ping the
workstation from the DC.

Customer has been down for 2 days. Please help.








.

Relevant Pages

  • Re: Domain Trouble / Windows Server 2k3
    ... run ipconfig /all and note the IP address listed for the DNS server. ... Then right click on the local area connection and select ... workstations had to be rebuilt and is running WinXP. ...
    (microsoft.public.windows.server.general)
  • Re: VPN Stability Router-Router SBS 2k3 STD 1 Nic Setup
    ... Nope just the workstations present. ... Inet VPN, router to router or not, is problematic in some parts of the ... Outlook connection to exchange dropping. ... Unable to access remote office shares from main office ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent - please help
    ... on the DC and at some point during the process of configuring the router, ... Ethernet adapter Local Area Connection: ... above, are we still looking at a misdirected DNS server, or is it ... All workstations use DHCP. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Strange connection problem :-/
    ... >> renewing the DHCP lease. ... You can put the IPs into the router as ... DNS server addresses by hand. ... cause session table to become filled with 'stale' connection data. ...
    (uk.telecom.broadband)
  • Re: Urgent - please help
    ... Did the router also provide the DNS server IP? ... All workstations use DHCP. ...
    (microsoft.public.windows.server.active_directory)