How to close LAN session and login as another credentials

[Guest]

I didn't find any solution since Windows 95 upto Window XP/2003 to close a
currently running file sharing session and login as another credentils on
remote computer in LAN.

For example if I'm accessing a file share in another computer in LAN as
guest user and later want to access a shared folder having sharing access
only to administrator, it uses the same guest logged-in session to access the
folder and denies access. Windows has to authenticate for different
credentials to access that folder but it don't so, currently one has to log
off and log in his windows to close all LAN sessions to log-in as different
credentials.

Is there any better solution to this problem in XP/2003 or will be in
incoming Vista.

 

[Ron Lowe]

I didn't find any solution since Windows 95 upto Window XP/2003 to close a
currently running file sharing session and login as another credentils on
remote computer in LAN.

For example if I'm accessing a file share in another computer in LAN as
guest user and later want to access a shared folder having sharing access
only to administrator, it uses the same guest logged-in session to access
the
folder and denies access. Windows has to authenticate for different
credentials to access that folder but it don't so, currently one has to
log
off and log in his windows to close all LAN sessions to log-in as
different
credentials.

Is there any better solution to this problem in XP/2003 or will be in
incoming Vista.

My ( possibly wrong ) understanding is that windows won't allow 2 concurrent
connections to the same server with different credentials. So you need to
fully disconnect from the server with the old credentials before attempting
to connect with new ones.

To fully disconnect without logging off and back on, try going to a command
prompt and issuing the command:

net use * /delete

Why don't you just log in as *you*, and set the permissions accordingly on
the server?
*you* would have permissions on the guest shares.
*you* would have permissions on the admin shares ( assuming *you* is a
member of the admins group on the server).

It seems crazy to have to log in as different usernames to access different
content.
Just log in as you, and set the permissions on the content properly.

 

[Guest]

I ran the command u told its not showing that session/connection with machine
in list neither my problem fixed. When I try to access administrator share
e.g. "\\machinename\c$" it pormpts for authentication but guest already
selected as user name and user name combo disabled it only allows me to enter
passwords for that already selected guest user.

This required sometimes when u require to temporarily access server's
administrative share from other user's machine to access any utility etc. and
then don't want to allow that user to access the same. All this procedure
can't be done without log off/closing apps.

I actually couldn't understand this strange behaviour of Windows, sometimes
it ask for UID/PWD when u access hidden administrative share even if you
already has connection as guest or other low privileged user but sometimes it
act as mentioned above with UID selected, disabled and sometimes it clearly
dnies access without any prompt.

One way I tackle this problem without log off and without closing apps is I
end explorer.exe process and then run explorer.exe as administrator user from
task manager, access the required share and then to shift back explorer.exe
to same previous user again end explorer.exe process and run it as that user.
It works but its a long process to do a simple thing.

I think MS should have to add some check box in authentication box to ask
user whether one wants to maintain session for the connection or temporarily
accessing it once (or session automatically expires after specified time)
etc. This is the problem since Windows 95 uptill now, I don't know y
Microsoftees didn't face this problem yet or if facing it y don't they want
to fix it.

Adil Akram

 

[Ron Lowe]

Ah, I see what you are trying to do.
I don't think there is an easy way to do this.

Let me see if I have this straight.
User Joe is logged in, and is connected to a share on the server.
You want to be able to lean over his shoulder, and connect to another share
on the same server, one which Joe has no permissions for, and supply
different username/password. However, you don't get the chance to supply
these credentials, since it will automatically try to use the credentials of
the existing session.

The problem is that from 1 login session on a PC, you cannot have 2 sessions
to the same server with different credentials. There really is not an
elegant way around that which I can think of.

Could you put the administrative stuff you want to access on a different
server? That would fix it.

If deleting connections with the command 'net use * /delete' didnt help,
then the only other thing I can think of is to stop and re-start the
workstation service. I don't know if it would help or not. I guess it
depends on whether there are any persistent mapped drives that would
automatically re-connect.