Discussion Locked

Remote clients can't connect beyond DC/DNS server

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My local network site consists of Win2003 DC/DNS server with a few member servers; as file servers, an intranet server, and ISA2004 as a gateway for internet connectivity.

Recently I'm required to connect a remote site with 3 xp-sp2 clients thru a TDM line to the local network (by using dedicated-for-this-connection Cisco routers). Routing between the two sites is ok. I can join the remote clients to the domain with no problem. I can ping the DC/DNS server and browse the shared folders located on it, I can also do RDC to it from the remote clients.

The problem is that none of these remote clients can go beyond the DC/DNS. They can't connect or even ping to any of the member servers or clients in the local network. I can do search in the active directory from them and can find the member servers but still refuse to connect to them, even if I logon to the clients using domain administrator account?!!!

Any help please? Thank you in advance

2 replies

by robo_dev

Windows, uses UDP (connectionless) protocol on port 88 by default for authentication. If MTU issues or latency causes fragmentation, then out-of-order packets create authentication failures.

It's a simple registry hack on the client side:

http://support.microsoft.com/kb/244474

The reason it does this stupid thing is to retain RFC complance with Kerberos.

by yas13899

Thank you robo_dev for the reply

I read the kb article, and I'm going to try the solution for sure.

But the thing is that I have no problem logging to the domain. I can logon with no error messages (only with a little delay which I guess when trying to map the home folder for the user, which is failed because it's located on a member server that can't be contacted). I don't know if this article would be applicable here ??

Regards

This discussion is closed to new replies.