Connecting to a Network Share

[Gabriel Martin]

Hi All

We have a Hp DL360 server running Windows Standard 2003 R2 using Smart Start 7.40 when ever a client either being Windows 2000 pro or XP tries to connect to a network share the following appears

System error 317 has occurred.

The system cannot find message text for message number 0x*** in the message file
for ***.

2003 server to 2003 server is ok has anyone else seen this problem before ?

Regards

Gabriel

[MikeOB]

Hi Gabriel,

Have you smart card enabled on these machines ?

http://support.microsoft.com/?kbid=885275

Michael O'Brien
TSG EMEA
http://www.hp.com/hps/
michael.obrien2@hp.com

[Arch_Muthiah]

Even MS did not provide the correct reson for this type of error, but from my understanding this kind of error behavior may occur if you use certain types of network adapters. check your network card and config


Archunan

[Gabriel Martin]

Micheal

I have seen that Microsoft Article and we dont use smart cards.

I guess I will check my network config including the cards

thanks

Gabriel

[Robert S. Carr]

Gabriel:

Are the servers in a domain or standalone? Are you using Active Directory?

If you find that the problem is not related to NIC drivers, you may try a little experiment.

1) Remove one of the servers from the domain.
2) Using another PC on the network, attempt to link to one of the machine's shares. You can use the machine's NetBIOS name or it's IP address. Try one or the other if fails to work.

If you can link to a share on a server when in standalone mode, rejoin the domin. Now at the command prompt of the servers where clients cannot logon type

net start

A list of services will appear. The service Net Logon should be one of the services. Now type

net stop "Net Logon"

wait a few seconds. Now type

net start "Net Logon"

It's a bit of stretch but the job of Net Logon is to pass user credentials to a domain controller and return domain security identifiers. I wonder if it's your security identifiers that aren't getting messed up effectively keeping you off the server.

Anyway, give some of the ideas a try and report back. I'm rather curious about what would cause this error and interested in it's solution. If what happened to you happened at our workplace it could be a potential disaster.

Rob

[Robert S. Carr]

Gabriel:

This article is interesting:

http://www.tokeshi.com/index.php?name=News&file=article&sid=3444

Are you running Terminal Services or Citrix?

Rob

[Gabriel Martin]

Rob

Thanks for your reply yes we are on Active Directory. I have done your experiment and found the following;

If I take the server off the domain and add it to a work group all clients connect fine. It prompts for username and password but all the security works.

Once I add it back in to the domain same error as the one I stated in the first thread of this article.

I now have to find out why AD is not working as it should....

thanks


Gabriel

[Alan_152]

Since you have mentioned that you are on an AD system, make sure your network stack and (particularly) your DDNS references are all correct and pingable with decent response times.