Windows client can't acces share on 2003 DC server
Posted on 2004-09-30
i need some Help :
I've two network, A and B, linked by a cisco VPN.
Network A contains :
- A server W2003 DC file server, GC, DNS
- W2000 and WXP clients
Network B contains :
- 1 W200 client
- 1 printer
The network settings have been verifyed many times ( DNS, IP, ...)
"A" cleints are able to access any shares on other A clients, on the DC, on B client. they can print by IP (port of the printer), to the B printer.
DC can access any share on B client, Browse the B printer config, telent B printer port 9100, etc..
But when i try to print from DC to B printer adress, as the A workstations, the job hangs, and restarts, and hangs, and restarts, with long time delay before each hang and each restart.
The same way, when i'm trying on the DC to install the shared B printer on the DC, error after 30 seconds.
From the other side, B client can't browse the DC, but can browse each other A clients, access their shares, etc. The only shares that B can browse on the DC are SYSVOL and NETLOGON
The B client isn't able to have a terminal service session to the DC. Not the uthentication, just when i give the name of the DC, or it's IP address, the RDP client says me Unable to find, after some seconds.
I'm able to open a VNC connexion to the DC, but as soon as the VNC session is authenticated the screen keeps grayed (no graphic is coming to the client session)
In the B client's eventviewer, I see some errors :
- 5788 and 5789 ... HOST DNS update.... time delayed , no response.... This errors seems to be discussed only about access error, or permissions , on the net, but that's not what I have for errors.
- And error that says that the strategy couldn't be fully retrieved. error 0.
The logon script executes well, indicates that the "Net use" finished succssfully. The drives appears in the explorer, but as soon as i'm trying to browse them, it's hanging three minutes, ant then i have a message that say's something like that "drive could not be mapped, it already exists", and sometimes an other error "the rpc server could not be contacted" or "The server service is not started".
I've have tried with another client, that i've put in the B network. That was my laptop. I didn't integrate it in the domain but i tested share browsing and terminal services to the DC. The same error appears ( for share browsing, of course i had to enter authetication credentials)
I tried to disjoin the client from domain, rename it, rejoin it. Not better.
I updated at max server and client, not better.
I had the network enginers to delete every filter in the cisco routers in order to be sure that everithing is going through without problem.
I tried to monitor client authentication, on the DC side, everithing seems OK : no error, also with full audit enabled.
I don't know how to continue my investigations.
Has someone ideas ?
thanks a lot