Sign in with
Sign up | Sign in
Your question

print cant find DC but its there anyway????

Last response: in Windows 2000/NT
Share
Anonymous
September 15, 2004 5:24:48 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi all,

(see below) I get this on a client every time it boots

I can get to the dc from the client in my network places
by navigating to it, and I can ping it by
its first name, its FQDN and its domain name.
and, its (the DC's) shared printer is accessable and I can print to it
from the client.

I also went to the dc and ran the dns tests in dns manager
and they all work.

the client is listed in dns on the dc. the clients nic
registers with dns.

How else can I verify dns or fix this problem?

Thank you in advance

James W. Long.




Event Type: Error
Event Source: Print
Event Category: None
Event ID: 33
Date: 9/14/2004
Time: 10:20:39 PM
User: NT AUTHORITY\SYSTEM
Computer: HAL9000
Description:
The PrintQueue Container could not
be found because the DNS Domain name
could not be retrieved. Error: 54b

event ID 33 - sort of infers "cant get information from the DC
due to dns problem sorta maybe if it applies in this case"

Error 0x54B (1355 decimal) =
"The specified domain either does not
exist or could not be contacted." -
Verify that you have connectivity
to the domain controller.
Verify DNS is functional.

More about : print find

Anonymous
September 16, 2004 12:40:08 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:xtqdnU4B7fG8T9rcRVn-sg@wideopenwest.com,
James W. Long <JamesLong@wowway.com> made a post then I commented below
> Hi all,
>
> (see below) I get this on a client every time it boots
>
> I can get to the dc from the client in my network places
> by navigating to it, and I can ping it by
> its first name, its FQDN and its domain name.
> and, its (the DC's) shared printer is accessable and I can print to it
> from the client.
>
> I also went to the dc and ran the dns tests in dns manager
> and they all work.
>
> the client is listed in dns on the dc. the clients nic
> registers with dns.
>
> How else can I verify dns or fix this problem?
>
> Thank you in advance
>
> James W. Long.
>
>
>
>
> Event Type: Error
> Event Source: Print
> Event Category: None
> Event ID: 33
> Date: 9/14/2004
> Time: 10:20:39 PM
> User: NT AUTHORITY\SYSTEM
> Computer: HAL9000
> Description:
> The PrintQueue Container could not
> be found because the DNS Domain name
> could not be retrieved. Error: 54b
>
> event ID 33 - sort of infers "cant get information from the DC
> due to dns problem sorta maybe if it applies in this case"
>
> Error 0x54B (1355 decimal) =
> "The specified domain either does not
> exist or could not be contacted." -
> Verify that you have connectivity
> to the domain controller.
> Verify DNS is functional.

Hi James,

Nice to see you back here!

As for the error, that is usually a DNS lookup problem. Can you verify that
all the SRV records exist under the zone? I remember we talked before about
your DNS configuration, so I believe that your systems are only using the
internal DNS, meaning that you are not using your ISP's other than as a
forwarder, correct?

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================
Anonymous
September 16, 2004 2:20:19 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Dear Ace:


yes, in every "_tcp" folder there are 1 to 3 SRV recs


and here(see below) is net share and nslookup for you.
nslookup shows the same result if executed from
the DC or the client.

Thanks,
James



----------------------------------------------------------------
C:\winnt:net share

Share name Resource Remark

--------------------------------------------------------------------
D$ D:\ Default share
print$ C:\WINNT\system32\spool\drivers Printer Drivers
ADMIN$ C:\WINNT Remote Admin
IPC$ Remote IPC
C$ C:\ Default share
C C:\
D D:\
NetInstalls C:\NetInstalls
NETLOGON C:\WINNT\SYSVOL\sysvol\jewelconsulting.org\SCRIPTS
Logon server share
SYSVOL C:\WINNT\SYSVOL\sysvol Logon server share
Users C:\Users
HPOJG85 LPT1: Spooled HP DeskJet 550C
The command completed successfully.


C:\winnt:nslookup
Default Server: jewelntserver.jewelconsulting.org
Address: 10.0.0.50

> set q=srv
> _ldap._tcp.jewelconsulting.org
Server: jewelntserver.jewelconsulting.org
Address: 10.0.0.50

_ldap._tcp.jewelconsulting.org SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = jewelntserver.jewelconsulting.org
jewelntserver.jewelconsulting.org internet address = 10.0.0.50






"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:%23vC$nY4mEHA.3428@TK2MSFTNGP11.phx.gbl...
> In news:xtqdnU4B7fG8T9rcRVn-sg@wideopenwest.com,
> James W. Long <JamesLong@wowway.com> made a post then I commented below
> > Hi all,
> >
> > (see below) I get this on a client every time it boots
> >
> > I can get to the dc from the client in my network places
> > by navigating to it, and I can ping it by
> > its first name, its FQDN and its domain name.
> > and, its (the DC's) shared printer is accessable and I can print to it
> > from the client.
> >
> > I also went to the dc and ran the dns tests in dns manager
> > and they all work.
> >
> > the client is listed in dns on the dc. the clients nic
> > registers with dns.
> >
> > How else can I verify dns or fix this problem?
> >
> > Thank you in advance
> >
> > James W. Long.
> >
> >
> >
> >
> > Event Type: Error
> > Event Source: Print
> > Event Category: None
> > Event ID: 33
> > Date: 9/14/2004
> > Time: 10:20:39 PM
> > User: NT AUTHORITY\SYSTEM
> > Computer: HAL9000
> > Description:
> > The PrintQueue Container could not
> > be found because the DNS Domain name
> > could not be retrieved. Error: 54b
> >
> > event ID 33 - sort of infers "cant get information from the DC
> > due to dns problem sorta maybe if it applies in this case"
> >
> > Error 0x54B (1355 decimal) =
> > "The specified domain either does not
> > exist or could not be contacted." -
> > Verify that you have connectivity
> > to the domain controller.
> > Verify DNS is functional.
>
> Hi James,
>
> Nice to see you back here!
>
> As for the error, that is usually a DNS lookup problem. Can you verify
that
> all the SRV records exist under the zone? I remember we talked before
about
> your DNS configuration, so I believe that your systems are only using the
> internal DNS, meaning that you are not using your ISP's other than as a
> forwarder, correct?
>
> --
> Regards,
> Ace
>
> Please direct all replies ONLY to the Microsoft public newsgroups
> so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees
> and confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
>
> Security Is Like An Onion, It Has Layers
> HAM AND EGGS: A day's work for a chicken;
> A lifetime commitment for a pig.
> --
> =================================
>
>
Related resources
Anonymous
September 16, 2004 3:33:00 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Ace, here is an update:

I prevented net dde and net dde dsdm services from autostarting on the
client,
removed the dc's printer and added it again,
and the problem went away.

Thanks,

James Long

ps have a few questions about howto install a w2k load for 15 systems
and want to clone that install from 1 and join them all to my domain but
fear renaming
the cloned installs afterward (so they have unique machine names). can you
help?, outside of
this forum or where? and how best to do my task in way short time.

Thanks, James





"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:%23vC$nY4mEHA.3428@TK2MSFTNGP11.phx.gbl...
> In news:xtqdnU4B7fG8T9rcRVn-sg@wideopenwest.com,
> James W. Long <JamesLong@wowway.com> made a post then I commented below
> > Hi all,
> >
> > (see below) I get this on a client every time it boots
> >
> > I can get to the dc from the client in my network places
> > by navigating to it, and I can ping it by
> > its first name, its FQDN and its domain name.
> > and, its (the DC's) shared printer is accessable and I can print to it
> > from the client.
> >
> > I also went to the dc and ran the dns tests in dns manager
> > and they all work.
> >
> > the client is listed in dns on the dc. the clients nic
> > registers with dns.
> >
> > How else can I verify dns or fix this problem?
> >
> > Thank you in advance
> >
> > James W. Long.
> >
> >
> >
> >
> > Event Type: Error
> > Event Source: Print
> > Event Category: None
> > Event ID: 33
> > Date: 9/14/2004
> > Time: 10:20:39 PM
> > User: NT AUTHORITY\SYSTEM
> > Computer: HAL9000
> > Description:
> > The PrintQueue Container could not
> > be found because the DNS Domain name
> > could not be retrieved. Error: 54b
> >
> > event ID 33 - sort of infers "cant get information from the DC
> > due to dns problem sorta maybe if it applies in this case"
> >
> > Error 0x54B (1355 decimal) =
> > "The specified domain either does not
> > exist or could not be contacted." -
> > Verify that you have connectivity
> > to the domain controller.
> > Verify DNS is functional.
>
> Hi James,
>
> Nice to see you back here!
>
> As for the error, that is usually a DNS lookup problem. Can you verify
that
> all the SRV records exist under the zone? I remember we talked before
about
> your DNS configuration, so I believe that your systems are only using the
> internal DNS, meaning that you are not using your ISP's other than as a
> forwarder, correct?
>
> --
> Regards,
> Ace
>
> Please direct all replies ONLY to the Microsoft public newsgroups
> so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees
> and confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
>
> Security Is Like An Onion, It Has Layers
> HAM AND EGGS: A day's work for a chicken;
> A lifetime commitment for a pig.
> --
> =================================
>
>
Anonymous
September 18, 2004 4:26:34 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:VaOdnWlsWbz2lNTcRVn-vw@wideopenwest.com,
James W. Long <JamesLong@wowway.com> made a post then I commented below
> Ace, here is an update:
>
> I prevented net dde and net dde dsdm services from autostarting on the
> client,
> removed the dc's printer and added it again,
> and the problem went away.
>
> Thanks,
>
> James Long
>
> ps have a few questions about howto install a w2k load for 15 systems
> and want to clone that install from 1 and join them all to my domain
> but fear renaming
> the cloned installs afterward (so they have unique machine names).
> can you help?, outside of
> this forum or where? and how best to do my task in way short time.
>
> Thanks, James
>

That's an interesting fix.

For cloning, the best method around (I'm sure others will have other
solutions), which doesn't work with domain controllers, is to use sysprep on
the servers, Ghost them, then multicast them out. BUT, if the server is once
configured with IIS, I do not believe the IUSR_machinename will change with
the new name. I don't think that will be much of a problem. I would
definitely check the host headers, and other machine specific settings. You
may be better off sysprepping them prior to configuring them, then configure
them individually after you cast them.

Ace
Anonymous
September 21, 2004 2:04:53 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Dear ace:

Ok that last was way over my head.
I just wanted to clone clients. but forget it now,
because they bought the systems without giving me a chance
to make a load and I'm already doing a brute force
round robin install. se'la vie.

I got MY network all back to normal, the
security db (secedit.sdb) was toast on one of my clients,
I repaired it and its back. very clean so far in error logs,
Im continuing to monitor those close till I get that
warm fuzzy feeling back.

catch ya later, I'm sure Ace.
Thanks for your awesome help.

James W. Long





"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:%23KY3zeTnEHA.3464@tk2msftngp13.phx.gbl...
> In news:VaOdnWlsWbz2lNTcRVn-vw@wideopenwest.com,
> James W. Long <JamesLong@wowway.com> made a post then I commented below
> > Ace, here is an update:
> >
> > I prevented net dde and net dde dsdm services from autostarting on the
> > client,
> > removed the dc's printer and added it again,
> > and the problem went away.
> >
> > Thanks,
> >
> > James Long
> >
> > ps have a few questions about howto install a w2k load for 15 systems
> > and want to clone that install from 1 and join them all to my domain
> > but fear renaming
> > the cloned installs afterward (so they have unique machine names).
> > can you help?, outside of
> > this forum or where? and how best to do my task in way short time.
> >
> > Thanks, James
> >
>
> That's an interesting fix.
>
> For cloning, the best method around (I'm sure others will have other
> solutions), which doesn't work with domain controllers, is to use sysprep
on
> the servers, Ghost them, then multicast them out. BUT, if the server is
once
> configured with IIS, I do not believe the IUSR_machinename will change
with
> the new name. I don't think that will be much of a problem. I would
> definitely check the host headers, and other machine specific settings.
You
> may be better off sysprepping them prior to configuring them, then
configure
> them individually after you cast them.
>
> Ace
>
>
Anonymous
September 21, 2004 8:53:25 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:ro6dnTk-acHZEdLcRVn-qg@wideopenwest.com,
James W. Long <JamesLong@wowway.com> made a post then I commented below
> Dear ace:
>
> Ok that last was way over my head.
> I just wanted to clone clients. but forget it now,
> because they bought the systems without giving me a chance
> to make a load and I'm already doing a brute force
> round robin install. se'la vie.
>
> I got MY network all back to normal, the
> security db (secedit.sdb) was toast on one of my clients,
> I repaired it and its back. very clean so far in error logs,
> Im continuing to monitor those close till I get that
> warm fuzzy feeling back.
>
> catch ya later, I'm sure Ace.
> Thanks for your awesome help.
>
> James W. Long
>

Sorry I was over your head on that and sorry to hear they slammed this on
you. I was just trying to simplify it. Good luck with everything!

Ace
!