Re: logon confusion

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


Thanks for the scolding.. I would justify my loathing for Exchange and, in
this instance, efforts to avoid making the pc part of the domain but I'll
spare everyone, some of you have heard my reasons before ;) Anyone know why
Exchange has a minimum POP3 server poll interval of 15 minutes? When you're
on the phone with someone waiting to see a document they sent .. that can be
a lifetime... at least now we can both watch youtube while we're waiting.

I tried to talk my client into a DC9 but they balked. So given they need to
run a 3rd party COM+ app, they needed SBS or Windows Server and SBS was
cheaper.

It's just that I can't understand why a local user Jill can log onto the
server from a pc that isn't added to the domain and create network places,
yet another new user say Jack on the same pc with the same group memberships
can't create the same network place.

I'll try the script, thanks.

Thanks for pushing AD best practices.. I know you mean well.

Michael

"Larry Struckmeyer" wrote:

My initial response is that if you want a car, buy a car. If you want a
truck, buy a truck. If you want a DC9 Caterpillar, buy one of those. But
don't expect the car to do what the DC9 does, or vice versa.

A non trusted user on a non trusted computer will receive a prompt for logon
credentials in a secure domain environment. If you think about this, you
would not want it any other way.

And as for allowing a non trusted user on a non trusted computer to modify
anything on the server, not in my thought process.

The user on the local computer is john.local. The user on the server is
john.domain. They are different users. They have the same name, but this
is not relevant to the server. It will reject john.local, as that user has
an unknown SID (security identifier).

And, for the concept of SBS "dictating things we don't want", you have the
wrong tool. I can't tell from your perspective if it is a horse and buggy
or a space shuttle in your scheme, but you want/need one and you have the
other.

--
Larry



"Dabbler" <Dabbler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A07B243-1C40-4B8B-81E8-C982467B0024@xxxxxxxxxxxxxxxx
I have a desktop (XP Pro SP2) that has been login in with a no longer
present
user. This logon works fine and the user is able to access share on the
SBS
2003 no problem. We now have a new user taking over this PC so I created a
new account (Administrator) on the pc and a new account on the server
(member
of Administrator's group, this is appropriate for this user). The computer
has never been a member of the domain.

We can log onto the pc with the local user id which is identical to the
server id (user id and passord) as we did with the previous user but now
we
are unable to create my network places shares. When we try to create one
with
the Other network and put in the resource URL \\myserver\mysharedfolder
and
the user mydomain/userid or userid@xxxxxxxxxxxxxx the dialog won't proceed
with the next button.

I'm relating all this having talked my client through this remotely. I
have
other computers running on that LAN which aren't members of the domain.
It's
a small shop so I'm reluctant to add them because then SBS tries to
dictate
things like default Outlook account is Exchange and other settings we
don't
want SBS fooling with and creating problems for us.

I guess what I'm looking for is minimal requirements (configuration) to
share resources on the SBS server without having the computer added to the
domain. I've done this before but I must be missing something because this
time it's not working.

Thanks for any suggestions.




.

Quantcast