Re: Clients not able to login to Domain

Russ,

As I mentioned earlier, the first workstation I tried this on was my laptop
and that worked ok. However, on subsequent attempts with other workstations
(all are XP Pro SP2), it appears as if login is normal but I am unable to
map any shares. As you point out below, it may be a "permissions" issue.
The difference I see is that I have added some extra permissions to my
account above the "user" level. Now if I can only figure out which one it
is . . . Any thoughts on where I should look? Thanks for your time and
help.

Tony

"Russ Grover" <russ@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ueKnPnCAGHA.2656@xxxxxxxxxxxxxxxxxxxxxxx
> Trying to figure out what your Problem is?
> You say Not able to login, but then your error is not able to map?
> Which is it?
>
> If you can access email easily then you are probably logged in.
>
> If it's just mapping; Is this ALL People or just one?
>
> If just one person, and everyone else can map to this source.
> I'd suspect a bad Local Profile on the PC
> (Delete it and recreate the local PC Profile)
>
> If more than one I'd say it's Permissions on the directory where you are
> trying to map to....
>
> Check both
>
> Russ
>
>
> --
> Russ Grover
> Small Business IT Support
> SBS Rocks!
> Portland/Beaverton OR
> Email: Sales at SmallBusinessITSupport.com
> Website: http://www.SmallBusinessITSupport.com
>
>
> "Tony" <tony@xxxxxxxxxxxxxx> wrote in message
> news:uJT3beCAGHA.292@xxxxxxxxxxxxxxxxxxxxxxx
>> I'm having an odd problem that I have not seen in this forum yet. I set
>> up
>> a new server with SBS 2k3 sp1. I created "arnold.local" for the domain.
>> I
>> have been adding our existing users to the domain one at a time using
>> http://server_name/ConnectComputer . This works for the initial login to
>> the
>> domain. The next day the user turns their computer on and gets the login
>> screen, enters their userid and password and everything appears to
>> connect
>> normally until we try to map a drive to the SBS 2K3 server and get the
>> error
>> message :
>>
>> "Arnold is not accessible. You might not have permission to use this
>> network resource. Contact the administrator of this server to find out if
>> you have access permissions.
>>
>> The network path was not found."
>>
>>
>> First, I have checked that the workstations in question are attempting to
>> connect to the "arnold.local" domain. I have also checked to make sure
>> that
>> they are getting their IP addresses from the SBS 2k3 server. During the
>> login process we get no indication that we have no access until we
>> attempt
>> to map a network share.
>>
>> Now it does look like it may have something to do with permissions, but I
>> really do not know where to begin. Any help or suggestions are most
>> appreciated.
>>
>> Tony
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Clients not able to login to Domain
    ... Passwords are supposed to remained synched between AD and Novell, ... it may be a "permissions" issue. ... >> You say Not able to login, but then your error is not able to map? ...
    (microsoft.public.windows.server.sbs)
  • Re: Clients not able to login to Domain
    ... You say Not able to login, but then your error is not able to map? ... If more than one I'd say it's Permissions on the directory where you are ... > The network path was not found." ...
    (microsoft.public.windows.server.sbs)
  • Re: Clients not able to login to Domain
    ... It is more likely to be permissions than a cached ... >> You say Not able to login, but then your error is not able to map? ... >>> to map a network share. ...
    (microsoft.public.windows.server.sbs)
  • Re: mapping disk in Vista not client
    ... Some one here have a idea how to configure to avoid the users to login ... in other workstations but let them to map a network drive in their own ...
    (microsoft.public.windows.server.sbs)
  • Re: How to find out if a login has permission for an obj?
    ... It will be the database user that has the permissions on the object and a ... given login will map onto that user. ... Check out the PERMISSIONS ([objectid ...
    (microsoft.public.sqlserver.programming)
Loading