Re: Printing when primary domain is down

Tech-Archive recommends: Fix windows errors by optimizing your registry

You need a DC at each loaction and you should have DNS on every DC.
You only have one domain,...there is no such thing as a "primary domain".


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Andre" <Andre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7C398E90-B0D0-4BD3-A500-18DD1CE1EC24@xxxxxxxxxxxxxxxx
One other question... I do have gobal catalog set as you stated and they
both
have dedicated AD site and subnet . However, on the NY server Because it's
not the primary domain I did not set up DNS, should I ?





"Lanwench [MVP - Exchange]" wrote:

Andre <Andre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Ok. This is going to be hard to explain please ask questions if you
have any. We are a small office and which is in NY and we have
another small office in MA. They are in the same Domain with the MA
office the primary Domain (Fireboxes at each end). Lately there has
been an issue with the ISP and connectivity (which is an issue with
the ISP). When connectivity drops of course we lose access to the
domain in MA. Not a huge deal in itself. we just reboot the cable
modem and after 10-15 min we get back up and running. The issue is
that for some reason when we lose connectivity to the domain a select
number of workstations have an issue talking to the network printers.
It's crazy but when this happens they can't open a word doc, excel
doc, they can't print, they cannot even bold a word in excel because
all of those operations are dependent on the printer and the
workstation can't talk to the printer. The question is why? The
printer is set up on the server in NY why does it matter if the
primary domain goes down? Also why is it only a select few
workstations? I've tried to reimage a workstation and still the same
issue. I've tried to change the user account and still same issue.
I've tried connecting the workstation to the printer by IP instead of
to the server and still same issue. I'm trying to work with the ISP
and getting this resolved but. it's taking them forever. Any
suggestions would be great!!

I presume both DCs are also GCs (global catalog servers)....if not, they
should be. Also, if the NY workstations authenticated to the DC in MA,
that
could explain a lot. Make sure each of your DCs is in its own dedicated
AD
Site & subnet (created in AD Sites & Services, and named appropriately).





.

Relevant Pages

  • Re: Printing when primary domain is down
    ... the ISP). ... When connectivity drops of course we lose access to the ... number of workstations have an issue talking to the network printers. ... Make sure each of your DCs is in its own dedicated AD ...
    (microsoft.public.windows.server.networking)
  • Re: SBS2k, no ISA, slow logon
    ... fix this and 90% of your other worries will disappear. ... > Workstations have static IP's and the DNS IP's are set to those of the ... > ISP. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... > the remote workstations lacked, ... > - workstations on the local subnet had no difficulty finding/joining yyy ...
    (microsoft.public.win2000.networking)
  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... The workstations in the same subnet as the DCs were able to join the ... >>Our DCs can write SRV records to the backbone DNS servers, ...
    (microsoft.public.win2000.networking)
  • Re: Remote Web Workplace connects to wrong desktop
    ... AD Computer Accounts which is what provides the lists of workstations available for RWW connections and then DNS and WINS tell the network how to resolve that name to and IP address. ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ...
    (microsoft.public.backoffice.smallbiz)