small test network help

Small test network at home. 1 W2k dc and 2 xp pro clients i netgear 5 port
switch( no internet involved). right off the bat I get "the system cannot
not log you on now because the domain grcc is not available". I know this is
pretty generic, but all I can find at MS is procedure for reinstall 128 bit
encryption files, seems a bit drastic? Where can I look?
Thanks
Frank l

If you log into one of the XP Pro clients with the local admin account, can
you ping the DC by name? Got an IP on the right network? What's doing DHCP,
presuming you use it?
Is the server multihomed?
What's your AD DNS setup? All servers and workstations should specify *only*
the internal AD-integrated DNS server's IP address in their network
settings. The AD-integrated DNS server should be set up with forwarders to
your ISP's DNS servers for external resolution. See
http://support.microsoft.com/default...b;en-us;300202 for more
info.

Frank wrote:
> Small test network at home. 1 W2k dc and 2 xp pro clients i netgear 5
> port switch( no internet involved). right off the bat I get "the
> system cannot not log you on now because the domain grcc is not
> available". I know this is pretty generic, but all I can find at MS
> is procedure for reinstall 128 bit encryption files, seems a bit
> drastic? Where can I look? Thanks
> Frank l

I think maybe I worded my questions wrong. When I said ni internet, I meant
there is no router, or any internet connection involved, I do not want one
for this setup right now. I will now check all the items you mentioned as
best I can and post back here.
Thanks very much
Frank


"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> If you log into one of the XP Pro clients with the local admin account,
can
> you ping the DC by name? Got an IP on the right network? What's doing
DHCP,
> presuming you use it?
> Is the server multihomed?
> What's your AD DNS setup? All servers and workstations should specify
*only*
> the internal AD-integrated DNS server's IP address in their network
> settings. The AD-integrated DNS server should be set up with forwarders to
> your ISP's DNS servers for external resolution. See
> http://support.microsoft.com/default...b;en-us;300202 for more
> info.
>
> Frank wrote:
> > Small test network at home. 1 W2k dc and 2 xp pro clients i netgear 5
> > port switch( no internet involved). right off the bat I get "the
> > system cannot not log you on now because the domain grcc is not
> > available". I know this is pretty generic, but all I can find at MS
> > is procedure for reinstall 128 bit encryption files, seems a bit
> > drastic? Where can I look? Thanks
> > Frank l
>
>

OK - then you don't need the forwarders in your AD DNS. The rest should
still apply - post back after you've tried!

Frank wrote:
> I think maybe I worded my questions wrong. When I said ni internet, I
> meant there is no router, or any internet connection involved, I do
> not want one for this setup right now. I will now check all the items
> you mentioned as best I can and post back here.
> Thanks very much
> Frank
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) ahoo.com> wrote in
> message news:(E-Mail Removed)...
>> If you log into one of the XP Pro clients with the local admin
>> account, can you ping the DC by name? Got an IP on the right
>> network? What's doing DHCP, presuming you use it?
>> Is the server multihomed?
>> What's your AD DNS setup? All servers and workstations should
>> specify *only* the internal AD-integrated DNS server's IP address in
>> their network settings. The AD-integrated DNS server should be set
>> up with forwarders to your ISP's DNS servers for external
>> resolution. See
>> http://support.microsoft.com/default...b;en-us;300202 for
>> more info.
>>
>> Frank wrote:
>>> Small test network at home. 1 W2k dc and 2 xp pro clients i netgear
>>> 5 port switch( no internet involved). right off the bat I get "the
>>> system cannot not log you on now because the domain grcc is not
>>> available". I know this is pretty generic, but all I can find at MS
>>> is procedure for reinstall 128 bit encryption files, seems a bit
>>> drastic? Where can I look? Thanks
>>> Frank l

>If you log into one of the XP Pro clients with the local admin account, can
you ping the DC by name?
No
>Got an IP on the right network?
Yes
>What's doing DHCP,
assigning IP to 2 winxp clients
>Is the server multihomed?
No
>What's your AD DNS setup?
This is where my problem is, I am sure.
>All servers and workstations should specify *only*
the internal AD-integrated DNS server's IP address in their network
settings.
They do.
Now here are errors from netdiag:
C:\>netdiag /test:dns


.......

Computer Name: MCSA1

DNS Host Name: mcsa1.grcc.com

System info : Windows 2000 Server (Build 2195)

Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel

List of installed hotfixes :

Q147222




Netcard queries test . . . . . . . : Passed




Per interface results:


Adapter : Local Area Connection

Netcard queries test . . . : Passed



Global results:




Domain membership test . . . . . . : Passed




NetBT transports test. . . . . . . : Passed

List of NetBt transports currently configured:

NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}

1 NetBt transport currently configured.





DNS test . . . . . . . . . . . . . : Failed

[WARNING] The DNS entries for this DC are not registered correctly on
DNS se

rver '192.168.1.1'. Please wait for 30 minutes for DNS server replication.

[FATAL] No DNS servers have the DNS records for this DC registered.

The command completed successfully

END



I have waited all day, configuration is screwy, I guess, but I cannot
correct it. Dumb, I know.



Here is dcdiag results:



C:\>dcdiag



Domain Controller Diagnosis



Performing initial setup:

Done gathering initial info.



Doing initial required tests



Testing server: Default-First-Site-Name\MCSA1

Starting test: Connectivity

3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's server GUID
DNS

name could not be resolved to an

IP address. Check the DNS server, DHCP, server name, etc

Although the Guid DNS name

(3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com) couldn't be

resolved, the server name (mcsa1.grcc.com) resolved to the IP
address

(192.168.1.1) and was pingable. Check that the IP address is

registered correctly with the DNS server.

......................... MCSA1 failed test Connectivity



Doing primary tests



Testing server: Default-First-Site-Name\MCSA1

Skipping all tests, because server MCSA1 is

not responding to directory service requests



Running enterprise tests on : grcc.com

Starting test: Intersite

......................... grcc.com passed test Intersite

Starting test: FsmoCheck

......................... grcc.com passed test FsmoCheck



I will keep looking and searching, but I figured this info would help with
finding my(proably stupid) problem

Frank L







"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:%(E-Mail Removed)...
> OK - then you don't need the forwarders in your AD DNS. The rest should
> still apply - post back after you've tried!
>
> Frank wrote:
> > I think maybe I worded my questions wrong. When I said ni internet, I
> > meant there is no router, or any internet connection involved, I do
> > not want one for this setup right now. I will now check all the items
> > you mentioned as best I can and post back here.
> > Thanks very much
> > Frank
> >
> >
> > "Lanwench [MVP - Exchange]"
> > <(E-Mail Removed) ahoo.com> wrote in
> > message news:(E-Mail Removed)...
> >> If you log into one of the XP Pro clients with the local admin
> >> account, can you ping the DC by name? Got an IP on the right
> >> network? What's doing DHCP, presuming you use it?
> >> Is the server multihomed?
> >> What's your AD DNS setup? All servers and workstations should
> >> specify *only* the internal AD-integrated DNS server's IP address in
> >> their network settings. The AD-integrated DNS server should be set
> >> up with forwarders to your ISP's DNS servers for external
> >> resolution. See
> >> http://support.microsoft.com/default...b;en-us;300202 for
> >> more info.
> >>
> >> Frank wrote:
> >>> Small test network at home. 1 W2k dc and 2 xp pro clients i netgear
> >>> 5 port switch( no internet involved). right off the bat I get "the
> >>> system cannot not log you on now because the domain grcc is not
> >>> available". I know this is pretty generic, but all I can find at MS
> >>> is procedure for reinstall 128 bit encryption files, seems a bit
> >>> drastic? Where can I look? Thanks
> >>> Frank l
>
>

Inline -

Frank wrote:
>> If you log into one of the XP Pro clients with the local admin
>> account, can
> you ping the DC by name?
> No

That sounds bad...

>> Got an IP on the right network?
> Yes

Can you ping the DC from a workstation by IP address?

>> What's doing DHCP,
> assigning IP to 2 winxp clients -

OK - I meant, what is running the DHCP server? Your DC?

>> Is the server multihomed?
> No

Good :-)

>> What's your AD DNS setup?
> This is where my problem is, I am sure.
>> All servers and workstations should specify *only*
> the internal AD-integrated DNS server's IP address in their network
> settings.
> They do.
> Now here are errors from netdiag:
> C:\>netdiag /test:dns
>
>
> ......
>
> Computer Name: MCSA1
>
> DNS Host Name: mcsa1.grcc.com
>
> System info : Windows 2000 Server (Build 2195)
>
> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
>
> List of installed hotfixes :
>
> Q147222
>
>
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
>
> Per interface results:
>
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
>
>
> Global results:
>
>
>
>
> Domain membership test . . . . . . : Passed
>
>
>
>
> NetBT transports test. . . . . . . : Passed
>
> List of NetBt transports currently configured:
>
> NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}
>
> 1 NetBt transport currently configured.
>
>
>
>
>
> DNS test . . . . . . . . . . . . . : Failed
>
> [WARNING] The DNS entries for this DC are not registered
> correctly on DNS se rver '192.168.1.1'. Please wait for 30 minutes for DNS
server
> replication.
>
> [FATAL] No DNS servers have the DNS records for this DC
> registered.
>
> The command completed successfully
>
> END
>
>
>
> I have waited all day, configuration is screwy, I guess, but I cannot
> correct it. Dumb, I know.
>
>
>
> Here is dcdiag results:
>
>
>
> C:\>dcdiag
>
>
>
> Domain Controller Diagnosis
>
>
>
> Performing initial setup:
>
> Done gathering initial info.
>
>
>
> Doing initial required tests
>
>
>
> Testing server: Default-First-Site-Name\MCSA1
>
> Starting test: Connectivity
>
> 3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's
> server GUID DNS
>
> name could not be resolved to an
>
> IP address. Check the DNS server, DHCP, server name, etc
>
> Although the Guid DNS name
>
> (3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com)
> couldn't be
>
> resolved, the server name (mcsa1.grcc.com) resolved to the IP
> address
>
> (192.168.1.1) and was pingable. Check that the IP address is
>
> registered correctly with the DNS server.
>
> ......................... MCSA1 failed test Connectivity
>
>
>
> Doing primary tests
>
>
>
> Testing server: Default-First-Site-Name\MCSA1
>
> Skipping all tests, because server MCSA1 is
>
> not responding to directory service requests
>
>
>
> Running enterprise tests on : grcc.com
>
> Starting test: Intersite
>
> ......................... grcc.com passed test Intersite
>
> Starting test: FsmoCheck
>
> ......................... grcc.com passed test FsmoCheck
>
>
>
> I will keep looking and searching, but I figured this info would help
> with finding my(proably stupid) problem
>
> Frank L
>

Naw, not a stupid question/problem at all. One generally learns more by
working with broken stuff!

1. Is 192.168.1.1 the IP address of your DC/server? I'm reckonin' so....
2. Do an ipconfig /all on both the server and on a client, and post them
here - you can pipe to a text file to make this easier. ipconfig /all
>c:\filename.txt
3. What's in your DHCP scope for the domain name setting? It needs to match
the server's - so it should be workstation.grcc.com since the server is
mcsa.grcc.com
4. Any services not started on the DC, such as the DNS client? Any errors in
the system or app log on the server?

<snip>

Hey,
I appreciate you sticking with me. Another Problem I ues a removable bay to
swap HD's. One has my regular crap, the other is the w2k server( the server
has no internet connection so I need to get off the net, swap drives , etc.
192.168.1.1 is the DC, scope is 192.168.1.3-192.168.1.10 , dhcp seems to be
working, both xp clients show .3 and .4 as ip's, which match what is in the
DC for leases. ipconfig shows OK, but I will post.Dns on clients is correct,
point to server. dns suffix is grcc.com(domain name. server is
mcsa1.grcc.com. Oh, my DC is also my dns, dhcp, etc, but I guess you knew
that.I will disconnect now and check the other things you mentioned. I'll be
back
Thanks
Frank
"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> Inline -
>
> Frank wrote:
> >> If you log into one of the XP Pro clients with the local admin
> >> account, can
> > you ping the DC by name?
> > No
>
> That sounds bad...
>
> >> Got an IP on the right network?
> > Yes
>
> Can you ping the DC from a workstation by IP address?
>
> >> What's doing DHCP,
> > assigning IP to 2 winxp clients -
>
> OK - I meant, what is running the DHCP server? Your DC?
>
> >> Is the server multihomed?
> > No
>
> Good :-)
>
> >> What's your AD DNS setup?
> > This is where my problem is, I am sure.
> >> All servers and workstations should specify *only*
> > the internal AD-integrated DNS server's IP address in their network
> > settings.
> > They do.
> > Now here are errors from netdiag:
> > C:\>netdiag /test:dns
> >
> >
> > ......
> >
> > Computer Name: MCSA1
> >
> > DNS Host Name: mcsa1.grcc.com
> >
> > System info : Windows 2000 Server (Build 2195)
> >
> > Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> >
> > List of installed hotfixes :
> >
> > Q147222
> >
> >
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> >
> > Per interface results:
> >
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> >
> >
> > Global results:
> >
> >
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> >
> >
> > NetBT transports test. . . . . . . : Passed
> >
> > List of NetBt transports currently configured:
> >
> > NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}
> >
> > 1 NetBt transport currently configured.
> >
> >
> >
> >
> >
> > DNS test . . . . . . . . . . . . . : Failed
> >
> > [WARNING] The DNS entries for this DC are not registered
> > correctly on DNS se rver '192.168.1.1'. Please wait for 30 minutes for
DNS
> server
> > replication.
> >
> > [FATAL] No DNS servers have the DNS records for this DC
> > registered.
> >
> > The command completed successfully
> >
> > END
> >
> >
> >
> > I have waited all day, configuration is screwy, I guess, but I cannot
> > correct it. Dumb, I know.
> >
> >
> >
> > Here is dcdiag results:
> >
> >
> >
> > C:\>dcdiag
> >
> >
> >
> > Domain Controller Diagnosis
> >
> >
> >
> > Performing initial setup:
> >
> > Done gathering initial info.
> >
> >
> >
> > Doing initial required tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Starting test: Connectivity
> >
> > 3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's
> > server GUID DNS
> >
> > name could not be resolved to an
> >
> > IP address. Check the DNS server, DHCP, server name, etc
> >
> > Although the Guid DNS name
> >
> > (3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com)
> > couldn't be
> >
> > resolved, the server name (mcsa1.grcc.com) resolved to the IP
> > address
> >
> > (192.168.1.1) and was pingable. Check that the IP address is
> >
> > registered correctly with the DNS server.
> >
> > ......................... MCSA1 failed test Connectivity
> >
> >
> >
> > Doing primary tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Skipping all tests, because server MCSA1 is
> >
> > not responding to directory service requests
> >
> >
> >
> > Running enterprise tests on : grcc.com
> >
> > Starting test: Intersite
> >
> > ......................... grcc.com passed test Intersite
> >
> > Starting test: FsmoCheck
> >
> > ......................... grcc.com passed test FsmoCheck
> >
> >
> >
> > I will keep looking and searching, but I figured this info would help
> > with finding my(proably stupid) problem
> >
> > Frank L
> >
>
> Naw, not a stupid question/problem at all. One generally learns more by
> working with broken stuff!
>
> 1. Is 192.168.1.1 the IP address of your DC/server? I'm reckonin' so....
> 2. Do an ipconfig /all on both the server and on a client, and post them
> here - you can pipe to a text file to make this easier. ipconfig /all
> >c:\filename.txt
> 3. What's in your DHCP scope for the domain name setting? It needs to
match
> the server's - so it should be workstation.grcc.com since the server is
> mcsa.grcc.com
> 4. Any services not started on the DC, such as the DNS client? Any errors
in
> the system or app log on the server?
>
> <snip>
>
>

Hi,
well, I have decided to start all over. I have fallen into a pretty common
group I fear. I learned (schools and books) how to install and configure W2k
and dcpromo, etc. I always knew windows really well, desktop support is my
forte, I guess. I have passed 210,215, 218. I have gotten a job(part time)
in a club with a small network(W2k DC, 11 clients, mixed mode). I add new
users, installed MS Mail and added all users to that (outlook), etc. Added a
few printers and a few new PC's. Anyway, I have forgotten the basics and
need to re learn. If you do not use it , you lose it, and considering I
never really had it, oh well. I am going to re format and start all over. I
see no other solution. Thanks so much for your help and time.
Regards,
Frank L
"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> Inline -
>
> Frank wrote:
> >> If you log into one of the XP Pro clients with the local admin
> >> account, can
> > you ping the DC by name?
> > No
>
> That sounds bad...
>
> >> Got an IP on the right network?
> > Yes
>
> Can you ping the DC from a workstation by IP address?
>
> >> What's doing DHCP,
> > assigning IP to 2 winxp clients -
>
> OK - I meant, what is running the DHCP server? Your DC?
>
> >> Is the server multihomed?
> > No
>
> Good :-)
>
> >> What's your AD DNS setup?
> > This is where my problem is, I am sure.
> >> All servers and workstations should specify *only*
> > the internal AD-integrated DNS server's IP address in their network
> > settings.
> > They do.
> > Now here are errors from netdiag:
> > C:\>netdiag /test:dns
> >
> >
> > ......
> >
> > Computer Name: MCSA1
> >
> > DNS Host Name: mcsa1.grcc.com
> >
> > System info : Windows 2000 Server (Build 2195)
> >
> > Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> >
> > List of installed hotfixes :
> >
> > Q147222
> >
> >
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> >
> > Per interface results:
> >
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> >
> >
> > Global results:
> >
> >
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> >
> >
> > NetBT transports test. . . . . . . : Passed
> >
> > List of NetBt transports currently configured:
> >
> > NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}
> >
> > 1 NetBt transport currently configured.
> >
> >
> >
> >
> >
> > DNS test . . . . . . . . . . . . . : Failed
> >
> > [WARNING] The DNS entries for this DC are not registered
> > correctly on DNS se rver '192.168.1.1'. Please wait for 30 minutes for
DNS
> server
> > replication.
> >
> > [FATAL] No DNS servers have the DNS records for this DC
> > registered.
> >
> > The command completed successfully
> >
> > END
> >
> >
> >
> > I have waited all day, configuration is screwy, I guess, but I cannot
> > correct it. Dumb, I know.
> >
> >
> >
> > Here is dcdiag results:
> >
> >
> >
> > C:\>dcdiag
> >
> >
> >
> > Domain Controller Diagnosis
> >
> >
> >
> > Performing initial setup:
> >
> > Done gathering initial info.
> >
> >
> >
> > Doing initial required tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Starting test: Connectivity
> >
> > 3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's
> > server GUID DNS
> >
> > name could not be resolved to an
> >
> > IP address. Check the DNS server, DHCP, server name, etc
> >
> > Although the Guid DNS name
> >
> > (3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com)
> > couldn't be
> >
> > resolved, the server name (mcsa1.grcc.com) resolved to the IP
> > address
> >
> > (192.168.1.1) and was pingable. Check that the IP address is
> >
> > registered correctly with the DNS server.
> >
> > ......................... MCSA1 failed test Connectivity
> >
> >
> >
> > Doing primary tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Skipping all tests, because server MCSA1 is
> >
> > not responding to directory service requests
> >
> >
> >
> > Running enterprise tests on : grcc.com
> >
> > Starting test: Intersite
> >
> > ......................... grcc.com passed test Intersite
> >
> > Starting test: FsmoCheck
> >
> > ......................... grcc.com passed test FsmoCheck
> >
> >
> >
> > I will keep looking and searching, but I figured this info would help
> > with finding my(proably stupid) problem
> >
> > Frank L
> >
>
> Naw, not a stupid question/problem at all. One generally learns more by
> working with broken stuff!
>
> 1. Is 192.168.1.1 the IP address of your DC/server? I'm reckonin' so....
> 2. Do an ipconfig /all on both the server and on a client, and post them
> here - you can pipe to a text file to make this easier. ipconfig /all
> >c:\filename.txt
> 3. What's in your DHCP scope for the domain name setting? It needs to
match
> the server's - so it should be workstation.grcc.com since the server is
> mcsa.grcc.com
> 4. Any services not started on the DC, such as the DNS client? Any errors
in
> the system or app log on the server?
>
> <snip>
>
>

I'm back, I know I took the easy way out, but I needed to get it right.
Anyway, I have one client Winxp pro that DOES connect and log in the server.
But still, my laptop gets the same not available error. I also turned up a
new error:
An error occured when dns was quired for the srv record used to locate a dc
for doamin grcc.com.
no connection could be made because the target machine actively refused it.
error 0x0000274D WSAECONNREFUSED
The query was for the SRV record for _ldap_tcp.dc_msdcs.grcc.com
Since my hp client can ping, logon, etc. I have to believe the problem is
with my other client. But they are identical as far as ipconfig goes(except
that the ip is 169 etc.apipa. The only difference is the hp client is a new
install xp pro and the laptiop(2nd client) has been used by me for the last
16 months for many reasons, including using the internet with my cable
modem.
However the DC shows a lease for the laptop and an ip address? This is
really frustrating. Sorry for the long post. Any ideas?
Thanks
Frank L

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> Inline -
>
> Frank wrote:
> >> If you log into one of the XP Pro clients with the local admin
> >> account, can
> > you ping the DC by name?
> > No
>
> That sounds bad...
>
> >> Got an IP on the right network?
> > Yes
>
> Can you ping the DC from a workstation by IP address?
>
> >> What's doing DHCP,
> > assigning IP to 2 winxp clients -
>
> OK - I meant, what is running the DHCP server? Your DC?
>
> >> Is the server multihomed?
> > No
>
> Good :-)
>
> >> What's your AD DNS setup?
> > This is where my problem is, I am sure.
> >> All servers and workstations should specify *only*
> > the internal AD-integrated DNS server's IP address in their network
> > settings.
> > They do.
> > Now here are errors from netdiag:
> > C:\>netdiag /test:dns
> >
> >
> > ......
> >
> > Computer Name: MCSA1
> >
> > DNS Host Name: mcsa1.grcc.com
> >
> > System info : Windows 2000 Server (Build 2195)
> >
> > Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> >
> > List of installed hotfixes :
> >
> > Q147222
> >
> >
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> >
> > Per interface results:
> >
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> >
> >
> > Global results:
> >
> >
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> >
> >
> > NetBT transports test. . . . . . . : Passed
> >
> > List of NetBt transports currently configured:
> >
> > NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}
> >
> > 1 NetBt transport currently configured.
> >
> >
> >
> >
> >
> > DNS test . . . . . . . . . . . . . : Failed
> >
> > [WARNING] The DNS entries for this DC are not registered
> > correctly on DNS se rver '192.168.1.1'. Please wait for 30 minutes for
DNS
> server
> > replication.
> >
> > [FATAL] No DNS servers have the DNS records for this DC
> > registered.
> >
> > The command completed successfully
> >
> > END
> >
> >
> >
> > I have waited all day, configuration is screwy, I guess, but I cannot
> > correct it. Dumb, I know.
> >
> >
> >
> > Here is dcdiag results:
> >
> >
> >
> > C:\>dcdiag
> >
> >
> >
> > Domain Controller Diagnosis
> >
> >
> >
> > Performing initial setup:
> >
> > Done gathering initial info.
> >
> >
> >
> > Doing initial required tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Starting test: Connectivity
> >
> > 3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's
> > server GUID DNS
> >
> > name could not be resolved to an
> >
> > IP address. Check the DNS server, DHCP, server name, etc
> >
> > Although the Guid DNS name
> >
> > (3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com)
> > couldn't be
> >
> > resolved, the server name (mcsa1.grcc.com) resolved to the IP
> > address
> >
> > (192.168.1.1) and was pingable. Check that the IP address is
> >
> > registered correctly with the DNS server.
> >
> > ......................... MCSA1 failed test Connectivity
> >
> >
> >
> > Doing primary tests
> >
> >
> >
> > Testing server: Default-First-Site-Name\MCSA1
> >
> > Skipping all tests, because server MCSA1 is
> >
> > not responding to directory service requests
> >
> >
> >
> > Running enterprise tests on : grcc.com
> >
> > Starting test: Intersite
> >
> > ......................... grcc.com passed test Intersite
> >
> > Starting test: FsmoCheck
> >
> > ......................... grcc.com passed test FsmoCheck
> >
> >
> >
> > I will keep looking and searching, but I figured this info would help
> > with finding my(proably stupid) problem
> >
> > Frank L
> >
>
> Naw, not a stupid question/problem at all. One generally learns more by
> working with broken stuff!
>
> 1. Is 192.168.1.1 the IP address of your DC/server? I'm reckonin' so....
> 2. Do an ipconfig /all on both the server and on a client, and post them
> here - you can pipe to a text file to make this easier. ipconfig /all
> >c:\filename.txt
> 3. What's in your DHCP scope for the domain name setting? It needs to
match
> the server's - so it should be workstation.grcc.com since the server is
> mcsa.grcc.com
> 4. Any services not started on the DC, such as the DNS client? Any errors
in
> the system or app log on the server?
>
> <snip>
>
>

Did you make the Laptop a Domain Member? Domain Membership isn't required
for it to have a lease in DHCP or a "A" record in DNS, but it does have to
be a Member to "login" to the Domain.

Personal Firewall (of any brand) running on the Laptop?

Did you scan the laptop for virus with AV Software that is verified to be
up-to-date?

Did you scan the laptop for Spyware using Ad-Aware (www.lavasoftusa.com) or
something else similar?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Frank" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm back, I know I took the easy way out, but I needed to get it right.
> Anyway, I have one client Winxp pro that DOES connect and log in the
server.
> But still, my laptop gets the same not available error. I also turned up a
> new error:
> An error occured when dns was quired for the srv record used to locate a
dc
> for doamin grcc.com.
> no connection could be made because the target machine actively refused
it.
> error 0x0000274D WSAECONNREFUSED
> The query was for the SRV record for _ldap_tcp.dc_msdcs.grcc.com
> Since my hp client can ping, logon, etc. I have to believe the problem is
> with my other client. But they are identical as far as ipconfig
goes(except
> that the ip is 169 etc.apipa. The only difference is the hp client is a
new
> install xp pro and the laptiop(2nd client) has been used by me for the
last
> 16 months for many reasons, including using the internet with my cable
> modem.
> However the DC shows a lease for the laptop and an ip address? This is
> really frustrating. Sorry for the long post. Any ideas?
> Thanks
> Frank L
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) ahoo.com> wrote in
message
> news:(E-Mail Removed)...
> > Inline -
> >
> > Frank wrote:
> > >> If you log into one of the XP Pro clients with the local admin
> > >> account, can
> > > you ping the DC by name?
> > > No
> >
> > That sounds bad...
> >
> > >> Got an IP on the right network?
> > > Yes
> >
> > Can you ping the DC from a workstation by IP address?
> >
> > >> What's doing DHCP,
> > > assigning IP to 2 winxp clients -
> >
> > OK - I meant, what is running the DHCP server? Your DC?
> >
> > >> Is the server multihomed?
> > > No
> >
> > Good :-)
> >
> > >> What's your AD DNS setup?
> > > This is where my problem is, I am sure.
> > >> All servers and workstations should specify *only*
> > > the internal AD-integrated DNS server's IP address in their network
> > > settings.
> > > They do.
> > > Now here are errors from netdiag:
> > > C:\>netdiag /test:dns
> > >
> > >
> > > ......
> > >
> > > Computer Name: MCSA1
> > >
> > > DNS Host Name: mcsa1.grcc.com
> > >
> > > System info : Windows 2000 Server (Build 2195)
> > >
> > > Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> > >
> > > List of installed hotfixes :
> > >
> > > Q147222
> > >
> > >
> > >
> > >
> > > Netcard queries test . . . . . . . : Passed
> > >
> > >
> > >
> > >
> > > Per interface results:
> > >
> > >
> > > Adapter : Local Area Connection
> > >
> > > Netcard queries test . . . : Passed
> > >
> > >
> > >
> > > Global results:
> > >
> > >
> > >
> > >
> > > Domain membership test . . . . . . : Passed
> > >
> > >
> > >
> > >
> > > NetBT transports test. . . . . . . : Passed
> > >
> > > List of NetBt transports currently configured:
> > >
> > > NetBT_Tcpip_{B3E60E3C-B933-4313-915A-8907B5A5BB30}
> > >
> > > 1 NetBt transport currently configured.
> > >
> > >
> > >
> > >
> > >
> > > DNS test . . . . . . . . . . . . . : Failed
> > >
> > > [WARNING] The DNS entries for this DC are not registered
> > > correctly on DNS se rver '192.168.1.1'. Please wait for 30 minutes for
> DNS
> > server
> > > replication.
> > >
> > > [FATAL] No DNS servers have the DNS records for this DC
> > > registered.
> > >
> > > The command completed successfully
> > >
> > > END
> > >
> > >
> > >
> > > I have waited all day, configuration is screwy, I guess, but I cannot
> > > correct it. Dumb, I know.
> > >
> > >
> > >
> > > Here is dcdiag results:
> > >
> > >
> > >
> > > C:\>dcdiag
> > >
> > >
> > >
> > > Domain Controller Diagnosis
> > >
> > >
> > >
> > > Performing initial setup:
> > >
> > > Done gathering initial info.
> > >
> > >
> > >
> > > Doing initial required tests
> > >
> > >
> > >
> > > Testing server: Default-First-Site-Name\MCSA1
> > >
> > > Starting test: Connectivity
> > >
> > > 3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com's
> > > server GUID DNS
> > >
> > > name could not be resolved to an
> > >
> > > IP address. Check the DNS server, DHCP, server name, etc
> > >
> > > Although the Guid DNS name
> > >
> > > (3588efed-4788-4d40-807e-938313628378._msdcs.grcc.com)
> > > couldn't be
> > >
> > > resolved, the server name (mcsa1.grcc.com) resolved to the IP
> > > address
> > >
> > > (192.168.1.1) and was pingable. Check that the IP address is
> > >
> > > registered correctly with the DNS server.
> > >
> > > ......................... MCSA1 failed test Connectivity
> > >
> > >
> > >
> > > Doing primary tests
> > >
> > >
> > >
> > > Testing server: Default-First-Site-Name\MCSA1
> > >
> > > Skipping all tests, because server MCSA1 is
> > >
> > > not responding to directory service requests
> > >
> > >
> > >
> > > Running enterprise tests on : grcc.com
> > >
> > > Starting test: Intersite
> > >
> > > ......................... grcc.com passed test Intersite
> > >
> > > Starting test: FsmoCheck
> > >
> > > ......................... grcc.com passed test FsmoCheck
> > >
> > >
> > >
> > > I will keep looking and searching, but I figured this info would help
> > > with finding my(proably stupid) problem
> > >
> > > Frank L
> > >
> >
> > Naw, not a stupid question/problem at all. One generally learns more by
> > working with broken stuff!
> >
> > 1. Is 192.168.1.1 the IP address of your DC/server? I'm reckonin' so....
> > 2. Do an ipconfig /all on both the server and on a client, and post them
> > here - you can pipe to a text file to make this easier. ipconfig /all
> > >c:\filename.txt
> > 3. What's in your DHCP scope for the domain name setting? It needs to
> match
> > the server's - so it should be workstation.grcc.com since the server is
> > mcsa.grcc.com
> > 4. Any services not started on the DC, such as the DNS client? Any
errors
> in
> > the system or app log on the server?
> >
> > <snip>
> >
> >
>
>