| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 840.1 | Open by another process? | OSLACT::OLAV | Do it in parallel! | Tue Jul 27 1993 04:11 | 6 |
| 840.2 | | LANDO::ALLISON | | Wed Jul 28 1993 12:32 | 8 |
| 840.3 | | DECWET::SCHREIBER | Be Here Now | Wed Jul 28 1993 13:19 | 3 |
| 840.4 | | MRPTH1::16.34.80.132::slab | labounty@mail.dec.com | Fri May 16 1997 11:16 | 20 |
|
What would prohibit me from accessing an NT area from
\\digital1\labounty even though that user is added with full control
to the area?
The area is \\mcgfs1\matl\slab, and that username has read access
starting at \\mcgfs1 and all the way down through to \slab.
I have been unable to access my directory at work pretty much
forever, or at least since I bought my laptop and started dialing in.
But that's "forever" to me, relatively speaking. For a short time I
was able to at least view the \slab directory, but apparently
something changed and I can't even do that any more.
Also, if the aforementioned username is listed as the owner of a file
or directory, what would prohibit that user from taking ownership of
the file or directory?
Thanks for any help/info.
|
| 840.5 | Share permissions? | RDVAX::akocstdhcp104-25.ako.dec.com::levy | Run Like an Antelope | Fri May 16 1997 11:20 | 3 |
| What are the share permissions?
dave
|
| 840.6 | | MRPTH1::16.34.80.132::slab | labounty@mail.dec.com | Fri May 16 1997 11:22 | 10 |
|
Darn, I figured I should have checked that first. 8^)
I was browsing around in here looking at access problems and noticed
that that had been mentioned as a possible culprit [access vs.
directory permissions].
So there's a good chance that that would be an excellent place to
start.
|
| 840.7 | | MRPTH1::16.34.80.132::slab | labounty@mail.dec.com | Fri May 16 1997 13:18 | 4 |
|
I was told that the entire group was given full control at the top
level of the share.
|
| 840.8 | What error logged on the server? | RDVAX::akocstdhcp104-25.ako.dec.com::levy | Run Like an Antelope | Fri May 16 1997 14:09 | 4 |
| What does the Security log on the server show as the error when the
user tries to connect?
dave
|
| 840.9 | | DECCXL::OUELLETTE | mudseason into blackfly season | Fri May 16 1997 14:28 | 10 |
| Also know that administrator accounts and guest accounts sometimes act
funny. Connecting like...
net use \\amachine\ipc$ /user:amachine\guest *
or
net use \\amachine\ipc$ /user:amachine\particular_user *
may be something you need to do.
|
| 840.10 | | AXPLAB::VLASIU | Sorin Vlasiu - Brussels, Belgium | Tue May 20 1997 11:30 | 6 |
| Re. Shawn
If both machines run NT, you may try to set the same password for
the user which is common to both machines.
Sorin
|
| 840.11 | | MRPTH1::16.34.80.132::slab | labounty@mail.dec.com | Tue May 20 1997 12:33 | 3 |
|
No, my laptop is running W95.
|
| 840.12 | | MPOS01::CERLING | im@miwitz.end | Tue May 20 1997 22:33 | 4 |
| Because your laptop is running W95, if you have the same user name on
NT as you have on W95, you must use the same password.
tgc
|
| 840.13 | | MRPTH1::16.121.160.237::slab | labounty@mail.dec.com | Wed May 21 1997 02:04 | 11 |
|
Wait a minute ... password?
The only password I need for network access is my \\digital1
password for Exchange.
The connection to the NT file server is password-less. Well, I have
a RAS password that's the same as my laptop's Windows
password ... but once I have a RAS connection there's no further
password needed.
|
| 840.14 | | AXPLAB::VLASIU | Sorin Vlasiu - Brussels, Belgium | Wed May 21 1997 05:25 | 4 |
| On \\msgfs1 user labounty should have the same password as
\\digital1\labounty. Try this.
Sorin
|
| 840.15 | | MRPTH1::16.34.80.132::slab | labounty@mail.dec.com | Wed May 21 1997 11:22 | 8 |
|
But I don't have a password, as far as I know.
My "accounts" are:
\\digital1\labounty
\\mcgfs1\matl\slab
|
| 840.16 | | MPOS01::16.135.176.202::Cerling | Call on the Calvary | Thu May 22 1997 08:10 | 14 |
|
If you have an account named labounty on a host, and you are logging
into your W95 desktop with the name labounty, unless your host and
your W95 are in the same domain (or there is a trust established),
you will have to have the same password in order to access from the
W95 client. If you are not using a password on a W95 client, most
likely, therein lies the problem. You desktop password does not
match your host password. This is true even if the file share is
set up for guest access. Because you have an account on the host,
it will try to validate that account. With an NT client it is nice
because you can access as a different user name; with W95, you
cannot.
tgc
|