problem connection on a share

[Guest]

Hello,

I have Windows 2000 server configured out of autonomous server. On this server a repertory is shared with the accesses everyone read. A station of another domain or Workgroup does not manage to reach it. Either it asks an authentification, or it posts: the user does not profit from the type of opening of session asked. Before this server was a controller of domain and there was no problem. On other domain of the same DC, not of problem either. I already looked in the local policy, access this computer from network. Everyone is put. I have already to haggle with the user guest and not of result either.
There would be somebody who had the same case and found a solution
Thank you in advance

"Sorry for my English"

 

[Pegasus \(MVP\)]

Your post is a little hard to understand, due to language difficulties. Let
me paraphrase your post:

- You have a Win2000 stand-alone server.
- You created a certain share on this server.
- Other machines on the network cannot connect to this share. They are
challenged for a password.

Here are a few things that are unclear:
- Is your server a domain controller?
- Do the problem machines get validated by this domain controller?
- Alternatively, do you operate in a workgroup environment where users get
validated locally?
- What operating system do the problem machines run?
- Do the users on the problem machine log on with the "Guest" account?

Hello,

I have Windows 2000 server configured out of autonomous server. On this

server a repertory is shared with the accesses everyone read. A station of
another domain or Workgroup does not manage to reach it. Either it asks an
authentification, or it posts: the user does not profit from the type of
opening of session asked. Before this server was a controller of domain and
there was no problem. On other domain of the same DC, not of problem
either. I already looked in the local policy, access this computer from
network. Everyone is put. I have already to haggle with the user guest and
not of result either.

 

[Guest]

- You have a Win2000 stand-alone server
YE
- You created a certain share on this server
YE
- Other machines on the network cannot connect to this share. They ar
challenged for a password
YES; either that or they receive a message stating the user does not have access right

Here are a few things that are unclear
- Is your server a domain controller
NO. But it USED to be one, it was "de-promoted". There still are 2 D.C.s in the domain
- Do the problem machines get validated by this domain controller
The client workstations are not in the same domain than the stand-alone server
- Alternatively, do you operate in a workgroup environment where users ge
validated locally
See abov
- What operating system do the problem machines run
Windows 2000 SP4 on all machine
- Do the users on the problem machine log on with the "Guest" account
No, they use an account from their own domain
There is a uni-directionnal trust from the workstation's domain to the server's domain (i.e. the workstation domain TRUSTS accounts from the server domain).

Hello

server a repertory is shared with the accesses everyone read. A station o
another domain or Workgroup does not manage to reach it. Either it asks a
authentification, or it posts: the user does not profit from the type o
opening of session asked. Before this server was a controller of domain an
there was no problem. On other domain of the same DC, not of proble
either. I already looked in the local policy, access this computer fro
network. Everyone is put. I have already to haggle with the user guest an
not of result either

 

[Pegasus \(MVP\)]

Make sure that the accounts/passwords used by your users are defined (with
identical passwords) on their domain controller ***and*** on the stand-alone
server. Furthermore, these accounts must ***not*** be locked out on the
stand-alone server.

- You have a Win2000 stand-alone server.
YES
- You created a certain share on this server.
YES
- Other machines on the network cannot connect to this share. They are
challenged for a password.
YES; either that or they receive a message stating the user does not have access rights

Here are a few things that are unclear:
- Is your server a domain controller?
NO. But it USED to be one, it was "de-promoted". There still are 2 D.C.s in the domain.
- Do the problem machines get validated by this domain controller?
The client workstations are not in the same domain than the stand-alone server.
- Alternatively, do you operate in a workgroup environment where users get
validated locally?
See above
- What operating system do the problem machines run?
Windows 2000 SP4 on all machines
- Do the users on the problem machine log on with the "Guest" account?
No, they use an account from their own domain.
There is a uni-directionnal trust from the workstation's domain to the

server's domain (i.e. the workstation domain TRUSTS accounts from the server
domain).