Hello Jennifer, much posts to night -
1)
Make sure you can ping your full AD domain name by FQDN from your clients as
well from your servers like ping company.com and get response.
2)
There can be a replication latency. Install Windows Server Support Tools
from your Windows Server CD.
Start -> Run !type! replmon !enter!
You can use Replication Monitor to manually replicate the directory.
3)
We gonna figure out if the printer objects actually exists in the directory
service at all.
Start-> Run !type! ADSIedit.msc !enter!
!Right click! ADSI Edit Node !Click Connect to! ->
!Select a well known Naming Context! Domain -> !Click! OK ->
!Click! Domain [<SERVER>.<DOMAIN>.<DOMAIN>]
!(You now gonna se the domain as you see it in AD Users and Computer)!
!(Navigate to one of your computer accounts and click on it, the computer
account is showed as a folder in ADSIEdit, How ever under the computer
account you should see the printers as an PrinteQueue Class)!
I hope some thing of this helps, I have a few more steps but I'm 17 years
old and have school to take care of too, try this if you think it can be to
any help.
--
Regards,
Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1
Jenifer Nech said:
I have a small network with 47 wkstns and 2 DC's. It has been 2 hrs
since
we
shared this printer. Is there a command line tool to get it listed sooner?
Are there published times we should wait?
I fear that something is wrong.