Re: Access local shares when DC is down

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Sorry for my delay. Create a regular account you would make on a domain. My
methodology will eliminate having to make a local profile for everyone.

Hope this helps,
--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts


<ACutsumbis@xxxxxxxxx> wrote in message
news:1150232308.415566.238810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The site is small, and i don't mind having to recreate users accounts
locally. The guest account just can NOT be enable, reguardless of how
much extra work it may require.

I understand that in a p2p network, there would be no gobal accounts,
but, the previous suggestion, was talking about creating one on the DC.

Thanks

Joshua Bolton wrote:
Of course enabling the guest account is a less than secure option. But
consider the request of "on the fly" changing from client/server to peer
to
peer networking. If you don't want to enable the guest account your only
option is to create a local account for EVERY person you want accessing
the
share when the server is down. This means x amount of wksts times x
amount
of users that you will have to sync their local account/password with the
pc
with the shares [along with their AD accouont passwds]. Then you have to
assign those users to those shares. Whew I get tired just thinking about
it.

Makes enabling the guest account look pretty easy doesn't it?

There are no "global" accounts in a peer to peer network!!! There is no
server/AD authenication if the DC is down.

*********************************************************

"So let's say we create a user called Share with a password of 123456 on
the
server. You would also create a local account on the workstation you wish
to
share from as Share \ 123456. Then for the logon script,

net use S: \\workstation\share 123456 /user:DOMAIN\Share /savecred "

Are you suggesting creating a user account on the server and all pcs
called
"share"? Looks to be just another name for "guest". AND you would put
the
local password in the script??? I would consider that far more insecure
than
enabling guest



.

Relevant Pages

  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Same question, still no answer!!!
    ... Sounds then like we are all paying for a feature set only large companies ... The "proxy server" pc is actually an older box stuffed ... Expectation #1) keep the ethernet more or less as is. ... The kids account would be ...
    (microsoft.public.windowsxp.basics)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Relay Problems
    ... The guest account was already disabled, even before this problem started 2 ... Set the diagnostics logging on the MSExchangeMU ... the server keeps on relaying! ...
    (microsoft.public.exchange.admin)
  • Sending email to mydomain.com
    ... server will appear as undeliverable. ... This happens because you are using the POP3 connector... ... an NDR when an account doesn't exist). ... >different from the user account names for the exchange ...
    (microsoft.public.windows.server.sbs)