Can't see shares when connection to DC is down.

We are having problems seeing shares on our member server at a branch office
when our connection to the main office is down. Our DC's are all at the main
office. We added WINS, and DNS to our member server and still no luck. When
we try to connect to the mapped drives it prompts us for a user name and
password. When we type in our username and password it tells us that it
already tried that username and password. All of our users are in Global
Groups, the Global Groups are then in Local Groups are given access to
shares. We also aren't able to see the printers share when the connection is
down. I need help on this soon.

You can't connect to shares when the DC is down.
That is why DCs aren't supposed to be down, and why the most attention to
uptime is always applied to DCs above all else.


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

"KO" <(E-Mail Removed)> wrote in message
news:5971CBBD-155A-4790-BCB9-(E-Mail Removed)...
> We are having problems seeing shares on our member server at a branch
> office
> when our connection to the main office is down. Our DC's are all at the
> main
> office. We added WINS, and DNS to our member server and still no luck.
> When
> we try to connect to the mapped drives it prompts us for a user name and
> password. When we type in our username and password it tells us that it
> already tried that username and password. All of our users are in Global
> Groups, the Global Groups are then in Local Groups are given access to
> shares. We also aren't able to see the printers share when the connection
> is
> down. I need help on this soon.

I am sorry let me restate that. Its not that the DC is down it’s that the
connection to the main office is down where the DC is located. The remote
site can't see the DC. If the user logs into their computer before the line
goes down they can continue working just fine but if they log in after the
line goes down they can't see the shares.

"Phillip Windell" wrote:

> You can't connect to shares when the DC is down.
> That is why DCs aren't supposed to be down, and why the most attention to
> uptime is always applied to DCs above all else.
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "KO" <(E-Mail Removed)> wrote in message
> news:5971CBBD-155A-4790-BCB9-(E-Mail Removed)...
> > We are having problems seeing shares on our member server at a branch
> > office
> > when our connection to the main office is down. Our DC's are all at the
> > main
> > office. We added WINS, and DNS to our member server and still no luck.
> > When
> > we try to connect to the mapped drives it prompts us for a user name and
> > password. When we type in our username and password it tells us that it
> > already tried that username and password. All of our users are in Global
> > Groups, the Global Groups are then in Local Groups are given access to
> > shares. We also aren't able to see the printers share when the connection
> > is
> > down. I need help on this soon.
>
>
>

"KO" <(E-Mail Removed)> wrote in message
news138CD1F-303C-43F4-BC33-(E-Mail Removed)...
>I am sorry let me restate that. Its not that the DC is down it's that the
> connection to the main office is down where the DC is located.

It's the same thing.

> site can't see the DC. If the user logs into their computer before the
> line
> goes down they can continue working just fine

The "cached account" is *local* to the machine and handles access to local
resources.

> but if they log in after the line goes down they can't see the shares.

Shares are *remote*, not local,....cached account doesn't help,...the DC is
required.


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

"KO" <(E-Mail Removed)> wrote in message
news138CD1F-303C-43F4-BC33-(E-Mail Removed)...
>I am sorry let me restate that. Its not that the DC is down it's that the
> connection to the main office is down where the DC is located. The remote

That is why there is supposed to be a DC at each location that replicate to
the other DCs......
That's why Active Directory has the "Sites Object",....to handle the
replication over the WAN links and be able to manage the replication if the
link is down for a while.

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

I need a way to allow my users to be able to keep working if there connection
to us is down. It doesn't happen very often but every now and then it does
go down and then we basically have to shut the plant down until the line is
back up. There has to be way to cache group rights on the member server so
they can keep running.

"Phillip Windell" wrote:

> "KO" <(E-Mail Removed)> wrote in message
> news138CD1F-303C-43F4-BC33-(E-Mail Removed)...
> >I am sorry let me restate that. Its not that the DC is down it's that the
> > connection to the main office is down where the DC is located.
>
> It's the same thing.
>
> > site can't see the DC. If the user logs into their computer before the
> > line
> > goes down they can continue working just fine
>
> The "cached account" is *local* to the machine and handles access to local
> resources.
>
> > but if they log in after the line goes down they can't see the shares.
>
> Shares are *remote*, not local,....cached account doesn't help,...the DC is
> required.
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

Have you read the replies to your previous messages?
* You require a DC in each remote location - replication to all, or at
least to the Main Office (Primary Domain Controller).
* You might be able to promote your member server to a backup DC at the
remote location, but we are unsure of it's OS.

KO wrote:
> I need a way to allow my users to be able to keep working if there connection
> to us is down. It doesn't happen very often but every now and then it does
> go down and then we basically have to shut the plant down until the line is
> back up. There has to be way to cache group rights on the member server so
> they can keep running.

Yes I read the replies. We have over 30 different locations witht the same
setup and they work just fine when the line goes down and none of them have
DCs. We would rather not have DCs at all of our sites.

"Trooper" wrote:

> Have you read the replies to your previous messages?
> * You require a DC in each remote location - replication to all, or at
> least to the Main Office (Primary Domain Controller).
> * You might be able to promote your member server to a backup DC at the
> remote location, but we are unsure of it's OS.
>
> KO wrote:
> > I need a way to allow my users to be able to keep working if there connection
> > to us is down. It doesn't happen very often but every now and then it does
> > go down and then we basically have to shut the plant down until the line is
> > back up. There has to be way to cache group rights on the member server so
> > they can keep running.
>
>

"KO" <(E-Mail Removed)> wrote in message
news:02DE63E2-75C3-4481-A29B-(E-Mail Removed)...
> Yes I read the replies. We have over 30 different locations witht the
> same
> setup and they work just fine when the line goes down and none of them
> have
> DCs.

Then they don't have the same setup. Examine them more closely.

We have about 40 sites. Currently each site is independent, each has own
Domain with own DCs. Later they will have a Master central Domain with
Child Domains at the Sites,...and yep,....at least 2 DCs at each location
and using AD Sites object to control replication over the WAN links.

It is the way it is .

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