Some other bits of information: the event log on the client periodically
gets the following warnings
Event ID 40961
"The Security System could not establish a secured connection with the
server DNS/myserver.mydomain.local. No authentication protocol was
available."
and 20 minutes later
"The Security System could not establish a secured connection with the
server cifs/myserver.mydomain.local. No authentication protocol was
available."
The server event log reports (but not at the same time)
Event ID 5513
"The computer MYCLIENT tried to connect to the server \\MYSERVER using the
trust relationship established by the MYDOMAIN domain. However, the computer
lost the correct SID when the domain was reconfigured. Re-establish the
trust relationship."
[I would if I knew how]
I hope someone can pick the bones out of this one.
Charles
"Charles Law" <(E-Mail Removed)> wrote in message
news:uBeI$(E-Mail Removed)...
>I see from the myriad of reports here that networking is fraught with
>problems. Does anyone know of a decent tool (GUI, not command-line) that
>can be run on a server and client to correct network problems?
>
> It seems to me that it should be possible to run a utility on the server
> and have it report all the anomalies and correct most of them. For
> example, I have a client that does not have a DNS registered on the
> server. Try as I might I cannot get it to happen. I know the IP address
> and I know the DN, so why can't I just tell some program and have it do
> it?
>
> I fully accept that networking is complicated, and that there are numerous
> configurations, but for that reason, why leave it to the likes of me to
> try to fix it when a program could do it so much more reliably? I have
> looked at the range of command-line tools supplied and they all have
> different syntax and require an in-depth knowledge of networking and its
> terminology. All I want is to get two machines talking to each other.
>
>
> You can probably tell that I am a bit frustrated ;-) and I do actually
> know a bit about networking, but clearly not enough to get this working?
>
> My problem, incidentally, relates to a Windows 2003 Server and an XP Pro
> client. The client can map drives on the server, but not vice-versa. My
> laptop works fine in both directions, but the server seems to know its DNS
> suffix. Not so the desktop client. I have read about forward and reverse
> lookups, and I've got some of those, but goodness knows whether they're
> right. How would I know?
>
> The client fails NetDiag on the DNS Test with "The DNS registration for
> 'MyClient.MyDomain.local' is incorrect on all DNS servers. How do I fix
> that?
>
> It also fails on the DC List Test with "You don't have access to DsBind to
> myserver (192.168.0.24). [ERROR_ACCESS_DENIED]"
>
> The Trust Relationship test fails with "Don't have access to test your
> domain sid for domain 'MyDomain'" and "Secure channel to domain 'MyDomain'
> is broken. [ERROR_NO_LOGON_SERVERS]". What's all that about?
>
> The server passes all NetDiag and DCDiag tests.
>
> Any ideas, anyone?
>
> Charles
>
>
|
Similar Threads
Linear Mode
