DNS issue Network bootdisk and 2003 domain

  • Thread starter Thread starter contactdellthornhill@gmail.com
  • Start date Start date
C

contactdellthornhill@gmail.com

Guest
I have a network bootdisk that worked perfect a week ago.

Basically, when I try to authenticate with the server, I get the "You
were logged on, but have not been validated by a server" error.

Upon investigation, I can ping IPs but not names.

Here's the kicker; I started a packet capturing utility (wireshark) on
both DNS servers (primary/secondary) and I can see ping requests come
if I ping their IPs, but when I ping their names I don't see any name
resolution requests. I'm not filtering any data except source IP in
Wireshark. So that tells me that the DNS request is never leaving the
computer. Which means that A) I have an improper configuration
setting on my bootdisk, even though I haven't changed any
configurations between now and the last time it worked or B) I'm
getting improper DHCP configs. But neither A or B make sense.

I have the "Microsoft network server (and client): Digitaly Sign
Communications (always)" and the "Send NT & NTLM authentication" GPO
policies set for my domain controllers. But that shouldn't knock down
DNS requests.

Any help would be great. Thanks!
 
Re: DNS issue Network bootdisk and 2003 domain

Hello contactdellthornhill@gmail.com,

Just to understand you correct, your network bootdisk was working without
any problem?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a network bootdisk that worked perfect a week ago.
>
> Basically, when I try to authenticate with the server, I get the "You
> were logged on, but have not been validated by a server" error.
>
> Upon investigation, I can ping IPs but not names.
>
> Here's the kicker; I started a packet capturing utility (wireshark) on
> both DNS servers (primary/secondary) and I can see ping requests come
> if I ping their IPs, but when I ping their names I don't see any name
> resolution requests. I'm not filtering any data except source IP in
> Wireshark. So that tells me that the DNS request is never leaving the
> computer. Which means that A) I have an improper configuration
> setting on my bootdisk, even though I haven't changed any
> configurations between now and the last time it worked or B) I'm
> getting improper DHCP configs. But neither A or B make sense.
>
> I have the "Microsoft network server (and client): Digitaly Sign
> Communications (always)" and the "Send NT & NTLM authentication" GPO
> policies set for my domain controllers. But that shouldn't knock down
> DNS requests.
>
> Any help would be great. Thanks!
>
 
Re: DNS issue Network bootdisk and 2003 domain

Hello contactdellthornhill@gmail.com,


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a network bootdisk that worked perfect a week ago.
>
> Basically, when I try to authenticate with the server, I get the "You
> were logged on, but have not been validated by a server" error.
>
> Upon investigation, I can ping IPs but not names.
>
> Here's the kicker; I started a packet capturing utility (wireshark) on
> both DNS servers (primary/secondary) and I can see ping requests come
> if I ping their IPs, but when I ping their names I don't see any name
> resolution requests. I'm not filtering any data except source IP in
> Wireshark. So that tells me that the DNS request is never leaving the
> computer. Which means that A) I have an improper configuration
> setting on my bootdisk, even though I haven't changed any
> configurations between now and the last time it worked or B) I'm
> getting improper DHCP configs. But neither A or B make sense.
>
> I have the "Microsoft network server (and client): Digitaly Sign
> Communications (always)" and the "Send NT & NTLM authentication" GPO
> policies set for my domain controllers. But that shouldn't knock down
> DNS requests.
>
> Any help would be great. Thanks!
>
 
Re: DNS issue Network bootdisk and 2003 domain

Yes, the bootdisk was working fine. I had just used it a couple weeks
prior to build eight machines without any hangups or problems.

And to clarify the situation a little more; I actually have the
"bootdisk" being hosted by a local RIS server. So the computer will
successfully contact the RIS server, and I'll go through the whole the
whole RIS client setup process (I select my ghost image and not my
standard XP build, obviously). During the client setup process a
computer account is created in Active Directory. So I know there's
nothing wrong with my DNS, DHCP or Active Directory servers, because
all those services are required for RIS to operate.
 
Re: DNS issue Network bootdisk and 2003 domain

Hello contactdellthornhill@gmail.com,

But you did not use the DOS bootdisk to connect completely to the server?
RIS takes over directly with PXE boot.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Yes, the bootdisk was working fine. I had just used it a couple weeks
> prior to build eight machines without any hangups or problems.
>
> And to clarify the situation a little more; I actually have the
> "bootdisk" being hosted by a local RIS server. So the computer will
> successfully contact the RIS server, and I'll go through the whole the
> whole RIS client setup process (I select my ghost image and not my
> standard XP build, obviously). During the client setup process a
> computer account is created in Active Directory. So I know there's
> nothing wrong with my DNS, DHCP or Active Directory servers, because
> all those services are required for RIS to operate.
>
 
Re: DNS issue Network bootdisk and 2003 domain

Hello contactdellthornhill@gmail.com,

But you did not use the DOS bootdisk to connect completely to the server?
RIS takes over directly with PXE boot.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Yes, the bootdisk was working fine. I had just used it a couple weeks
> prior to build eight machines without any hangups or problems.
>
> And to clarify the situation a little more; I actually have the
> "bootdisk" being hosted by a local RIS server. So the computer will
> successfully contact the RIS server, and I'll go through the whole the
> whole RIS client setup process (I select my ghost image and not my
> standard XP build, obviously). During the client setup process a
> computer account is created in Active Directory. So I know there's
> nothing wrong with my DNS, DHCP or Active Directory servers, because
> all those services are required for RIS to operate.
>
 
Re: DNS issue Network bootdisk and 2003 domain

I do use a DOS bootdisk - at least disk image

After the initial RIS setup is complete, RIS kicks off a boot loader
that starts the installation of Windows. In my case, I have a
modified loader that I obtained from Symantec and instead of kicking
off a Windows installation, it loads a floppy image. And when that
floppy image starts loading it acts and behaves the same as if I had
stuck a floppy disk in the drive and powered the computer on - there's
no difference. Any ties to the DHCP, DNS and AD services are severed
until the network bootdisk re-creates those connections.

Not to mention this is the exact same configuration that was working
the last time I imaged my computers.
 
Back
Top