Log in

View Full Version : A Challenge - Network Shares, Wifi, PPCs, Domains!


Jon Westfall
10-14-2005, 08:48 PM
Ok, here is a challenging situation that I'm really at a loss for, so I'm hoping someone else has had experience and may be able to give me some ideas.

I have a domain set up and 2 domain controllers in it, Machiavelli & Rasputin. Machiavelli is a windows 2003 server, while Rasputin is a 2000 box. Otherwise, they are both DCs, and both functioning normally. Fairly stock configurations out of the box, with the only modifications being security settings in the DC security policy.

I have multiple Pocket PC's with Wifi, and they all exhibit this problem. They can map and access network drives on Machiavelli (I provide my domain username / password of course) but not on Rasputin. Whenever they try to connect to Rasputin, they get a Login Failed notice and I get prompted for my password. Enter password, login failed, repeat, etc... I've used Resco Explorer to try to view the folders on Rasputin and can't even do that - however the same exact credentials let me view the folders on Machiavelli.

Further boggling my mind is that Rasputin's network shares are seen by other computers inside and outside the domain when the correct credentials are provided! This looks like a specific PPC / Win2k DC problem.

So any help anyone can give would be appreciated. I'm really desperate here!

jpf
10-14-2005, 11:50 PM
are the servers both PDCs? are they on separate segments? have you set up a trust relationship between them?

Jon Westfall
10-15-2005, 05:39 AM
The servers are both DCs for the same domain. Since I'm not getting errors in the event log for authentication failures, I think my username/password aren't even being tried correctly. No errors for anything related to DNS / WINS in the event log either, unfortunatly.

Jon.

jpf
10-15-2005, 01:32 PM
are you including the domain in the username? i.e.
\\rasputin\user1

Jon Westfall
10-15-2005, 06:45 PM
are you including the domain in the username? i.e.
\\rasputin\user1

Yep, Tried that and about a hundred other variations. Like I said, I'm no longer believing it's a true authentication error, now I'm thinking it might be a communication problem.