A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Please wait while the domain list is created.



 
 
Thread Tools Display Modes
  #1  
Old April 19th 05, 09:23 PM
sean
external usenet poster
 
Posts: n/a
Default Please wait while the domain list is created.

Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this on
my network and it is the case. According to all the other threads and other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network and
it is pointing to iself for DNS with hints to fall back on and it hands out
the info to the clients via DHCP, where they receive the only DNS info is the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks
Ads
  #2  
Old April 19th 05, 10:10 PM
Ron Lowe
external usenet poster
 
Posts: n/a
Default

"sean" wrote in message
...
Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this
on
my network and it is the case. According to all the other threads and
other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network
and
it is pointing to iself for DNS with hints to fall back on and it hands
out
the info to the clients via DHCP, where they receive the only DNS info is
the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks



Is this affecting one machine, or many machines?
Anything in the event viewer of the problem machines?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


  #3  
Old April 19th 05, 10:17 PM
Ron Lowe
external usenet poster
 
Posts: n/a
Default

"sean" wrote in message
...
Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this
on
my network and it is the case. According to all the other threads and
other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network
and
it is pointing to iself for DNS with hints to fall back on and it hands
out
the info to the clients via DHCP, where they receive the only DNS info is
the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks



Here's some additional info on how to test the DNS configuration
on the problem machines.

This will test if the machine can find the records in DNS.

Do an ipconfig /all and see what DNS servers are listed.
It should only be the internal DNS servers which host the
domain's records, not an external ISP's DNS server.

Then test the DNS lookup like this:

Go to a command prompt.
Type "nslookup".
Then type "set type=all"
Then type "_ldap._tcp.dc._msdcs.domainname
(where domainname is the name of your domain).

Nslookup returns one or more SRV service location records in the following
format:

hostname.domainname internet address = ipaddress

where 'hostname' is the host name of a domain controller, 'domainname' is
the
domain to which the domain controller belongs, and ipaddress is the domain
controller's Internet Protocol (IP) address.

Then 'exit' will quit you out of nslookup.

Here's a screen-dump of me doing this on an XP machine joined to my domain,
"homenet.local.":

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local
Address: 81.187.191.78

( Check that the IP address of the DNS server being queried is correct.
You may get a warning if it can't reverse lookup the name of the default
server, this is sloppy but non-fatal. )

set type=all
_ldap._tcp.dc._msdcs.homenet.local.

Server: homenetdc01.homenet.local
Address: 81.187.191.78

_ldap._tcp.dc._msdcs.homenet.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = homenetdc01.homenet.local
homenetdc01.homenet.local internet address = 81.187.191.78
exit


Do you get the same?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


  #4  
Old April 20th 05, 03:56 PM
sean
external usenet poster
 
Posts: n/a
Default

No, I sure don't. I receive; server: unknown & address: 10.50.20.1 (which is
correct) nothing more after that. I've looked at the server and it appears to
be correct, but you can tell I'm no DNS wizard.

"Ron Lowe" wrote:

"sean" wrote in message
...
Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this
on
my network and it is the case. According to all the other threads and
other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network
and
it is pointing to iself for DNS with hints to fall back on and it hands
out
the info to the clients via DHCP, where they receive the only DNS info is
the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks



Here's some additional info on how to test the DNS configuration
on the problem machines.

This will test if the machine can find the records in DNS.

Do an ipconfig /all and see what DNS servers are listed.
It should only be the internal DNS servers which host the
domain's records, not an external ISP's DNS server.

Then test the DNS lookup like this:

Go to a command prompt.
Type "nslookup".
Then type "set type=all"
Then type "_ldap._tcp.dc._msdcs.domainname
(where domainname is the name of your domain).

Nslookup returns one or more SRV service location records in the following
format:

hostname.domainname internet address = ipaddress

where 'hostname' is the host name of a domain controller, 'domainname' is
the
domain to which the domain controller belongs, and ipaddress is the domain
controller's Internet Protocol (IP) address.

Then 'exit' will quit you out of nslookup.

Here's a screen-dump of me doing this on an XP machine joined to my domain,
"homenet.local.":

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local
Address: 81.187.191.78

( Check that the IP address of the DNS server being queried is correct.
You may get a warning if it can't reverse lookup the name of the default
server, this is sloppy but non-fatal. )

set type=all
_ldap._tcp.dc._msdcs.homenet.local.

Server: homenetdc01.homenet.local
Address: 81.187.191.78

_ldap._tcp.dc._msdcs.homenet.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = homenetdc01.homenet.local
homenetdc01.homenet.local internet address = 81.187.191.78
exit


Do you get the same?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking



  #5  
Old April 20th 05, 03:59 PM
sean
external usenet poster
 
Posts: n/a
Default

Currently, it's just the one machine, but this machine is to become the base
image for the rest of the deployment (34 more machines).

"Ron Lowe" wrote:

"sean" wrote in message
...
Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this
on
my network and it is the case. According to all the other threads and
other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network
and
it is pointing to iself for DNS with hints to fall back on and it hands
out
the info to the clients via DHCP, where they receive the only DNS info is
the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks



Is this affecting one machine, or many machines?
Anything in the event viewer of the problem machines?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking



  #6  
Old April 20th 05, 04:43 PM
Ron Lowe
external usenet poster
 
Posts: n/a
Default

"sean" wrote in message
...
No, I sure don't. I receive; server: unknown & address: 10.50.20.1 (which
is
correct) nothing more after that. I've looked at the server and it appears
to
be correct, but you can tell I'm no DNS wizard.


This section:

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local
Address: 81.187.191.78


is nslookup telling you want DNS server it's using.
So long as the IP address is correct, then it's OK.
The server name will only appear if you have set up something called Reverse
Lookup on the DNS server. If you have not, it will appear as unknown.
This is not a fatal error condition, and is not the source of your problem.
Many people don't set up their reverse DNS.

Moving on to the next section, we are trying to query the DNS server.
It's a big problem if we can't query it correctly.
This is the source of your problem.

First off, ensure the machine is actually reachable.
Can you ping 10.50.20.1 from a command prompt?
If it's not reachable, you need to look at your IP address, subnet mask, and
gateway settings.

If it IS reachable, try a simple lookup of the domain-controller's A-record:

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local -- don't worry about this.
Address: 81.187.191.78 -- check its still right

homenetdc01 --just enter the Domain Controller's name.

Server: homenetdc01.homenet.local --nslookup is querying this server..
Address: 81.187.191.78 -- at this IP address..

Name: homenetdc01.homenet.local -- for this name..
Address: 81.187.191.78 -- and got this response.

exit


If this basic nslookup query fails, then theres a big problem.
We need to determine if it's a client-side problem, or a server-side
problem.

Repeat this nslookup on a known-good machine.
Did it work there?
Does this nslookup command work from any machine?

If its a client side fault, then possible causes a

- Misconfigured firewall not permitting DNS replies;
- Incorrectly removed firewall causing general TCP/IP mayhem.
( has there ever been anything like ZoneAlarm installed then removed? )
- Bad entries in hosts file
- Re-pointed hosts file to malicious hosts file ( malware induced );
- Broken LSP stack caused by spyware removal ( LSPfix usually fixes. )

I think that's pretty much all the causes of DNS failure I can think of on
the client.

Server side:

Problems might include:

- Misconfigured firewall not permitting in DNS queries
( perhaps from only a certain range of IP addresses );

- DNS server service not running.

- No correct records in DNS.

Go to the DNS console, and expand up the forward lookup zones.
Is the domain there?
Can you see the A-records for the domain controller?
Can you nslookup on the server against itself?

Ensure the zone is set for Dynamic Update.
Use ipconfig /registerdns on the server to re-register itself with DNS
if the records are missing.

Try a 'dcdiag' from the command prompt to run some diagnostics.



--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


  #7  
Old April 26th 05, 11:08 PM
sean
external usenet poster
 
Posts: n/a
Default

Ron,

Thank you for all of your help, I kind of feel like an idiot for not
noticing, but this box is destined for public use and I started with
another's image file as a base, so what's happening here is that all of the
files and folders off of the root had their hidden attributes marked on and I
never noticed, because in the administrators profile, it was set to view
hidden and system files. So with the hidden attrib disabled, all is well.

Thanks again.

"Ron Lowe" wrote:

"sean" wrote in message
...
No, I sure don't. I receive; server: unknown & address: 10.50.20.1 (which
is
correct) nothing more after that. I've looked at the server and it appears
to
be correct, but you can tell I'm no DNS wizard.


This section:

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local
Address: 81.187.191.78


is nslookup telling you want DNS server it's using.
So long as the IP address is correct, then it's OK.
The server name will only appear if you have set up something called Reverse
Lookup on the DNS server. If you have not, it will appear as unknown.
This is not a fatal error condition, and is not the source of your problem.
Many people don't set up their reverse DNS.

Moving on to the next section, we are trying to query the DNS server.
It's a big problem if we can't query it correctly.
This is the source of your problem.

First off, ensure the machine is actually reachable.
Can you ping 10.50.20.1 from a command prompt?
If it's not reachable, you need to look at your IP address, subnet mask, and
gateway settings.

If it IS reachable, try a simple lookup of the domain-controller's A-record:

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local -- don't worry about this.
Address: 81.187.191.78 -- check its still right

homenetdc01 --just enter the Domain Controller's name.

Server: homenetdc01.homenet.local --nslookup is querying this server..
Address: 81.187.191.78 -- at this IP address..

Name: homenetdc01.homenet.local -- for this name..
Address: 81.187.191.78 -- and got this response.

exit


If this basic nslookup query fails, then theres a big problem.
We need to determine if it's a client-side problem, or a server-side
problem.

Repeat this nslookup on a known-good machine.
Did it work there?
Does this nslookup command work from any machine?

If its a client side fault, then possible causes a

- Misconfigured firewall not permitting DNS replies;
- Incorrectly removed firewall causing general TCP/IP mayhem.
( has there ever been anything like ZoneAlarm installed then removed? )
- Bad entries in hosts file
- Re-pointed hosts file to malicious hosts file ( malware induced );
- Broken LSP stack caused by spyware removal ( LSPfix usually fixes. )

I think that's pretty much all the causes of DNS failure I can think of on
the client.

Server side:

Problems might include:

- Misconfigured firewall not permitting in DNS queries
( perhaps from only a certain range of IP addresses );

- DNS server service not running.

- No correct records in DNS.

Go to the DNS console, and expand up the forward lookup zones.
Is the domain there?
Can you see the A-records for the domain controller?
Can you nslookup on the server against itself?

Ensure the zone is set for Dynamic Update.
Use ipconfig /registerdns on the server to re-register itself with DNS
if the records are missing.

Try a 'dcdiag' from the command prompt to run some diagnostics.



--
Best Regards,
Ron Lowe
MS-MVP Windows Networking



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Creating Domain list when joining a Windows XP Pro Workstation aoscott Windows XP Help and Support 2 June 10th 05 07:54 PM
invalid domain created at installation Floyd Windows XP Help and Support 1 April 14th 05 03:40 AM
"Please wait while domain list is created" Eddie Networking and the Internet with Windows XP 1 November 24th 04 03:27 PM
Problem getting a new XP computer to join an NT 4.0/Win 98 domain Stephen Porter Networking and the Internet with Windows XP 6 November 5th 04 11:57 AM
Adding XP Pro to NT Domain [email protected] Networking and the Internet with Windows XP 8 August 3rd 04 03:49 AM






All times are GMT +1. The time now is 09:07 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.