C
cdn1967
I hope someone can offer some insight here.
I work in a 140+ PC network using a Windows Domain (Windows 2000
Server) and a mix of PCs running withwer Windows XP pro or Windows 2000
pro. Our file server is Linux (Debian).
All works well for most functions. However there is one puzzle. When
I am installing something on an end user's PC, I need to install it
under my own profile (administrator rights) and access a directory on
that file server, as that is where the install files are located.
When I click Start --> Run --> "\\server-name" it prompts me, as
expected, for an account with admin rights. But when I enter my user
name and password, it says "access denied".
I did some basic troubleshooting, and here are some other points:
1) While logged on as the user, I discovered that if I disconnect all
mapped drives to that server, I can then access the server and installs
file upon entering my credentials.
2) If I log the user off and log on as myself (admin), I can install
everything with out a hitch.
I am working around my issue using one of the two methods above, but
would really prefer to simply connect to the share on the server as
myself without these technical gymnastics.
Thoughts? Any feed back would be greatly appreciated.
Keith Richmond
I work in a 140+ PC network using a Windows Domain (Windows 2000
Server) and a mix of PCs running withwer Windows XP pro or Windows 2000
pro. Our file server is Linux (Debian).
All works well for most functions. However there is one puzzle. When
I am installing something on an end user's PC, I need to install it
under my own profile (administrator rights) and access a directory on
that file server, as that is where the install files are located.
When I click Start --> Run --> "\\server-name" it prompts me, as
expected, for an account with admin rights. But when I enter my user
name and password, it says "access denied".
I did some basic troubleshooting, and here are some other points:
1) While logged on as the user, I discovered that if I disconnect all
mapped drives to that server, I can then access the server and installs
file upon entering my credentials.
2) If I log the user off and log on as myself (admin), I can install
everything with out a hitch.
I am working around my issue using one of the two methods above, but
would really prefer to simply connect to the share on the server as
myself without these technical gymnastics.
Thoughts? Any feed back would be greatly appreciated.
Keith Richmond