Networking Forums

Networking Forums > Computer Networking > Windows Networking > 2000 <-> 2003 networking problem

Reply
Thread Tools Display Modes

2000 <-> 2003 networking problem

 
 
Brian
Guest
Posts: n/a

 
      05-17-2006, 08:16 PM
Hi all. I've tried just about everything I can think of to resolve this, and
need some advise. I've got 3 DCs in a mixed mode domain...DC1 is 2000, DC2
and DC3 are 2003. If a user logs into a workstation and DC3 authenticated
them, the user couldn't access ANlY shares on DC1, but could on DC2 and DC3.
They'd get an error "Configuration information could not be read from the
domain controller, either because the machine is unavailable, or access has
been denied". However, if DC1 or DC2 authenticated the user, they could
access everything on every server without any problems.

The only difference I found between DC2 and DC3 is that DC2 wasn't listed in
WINS database. So, on DC2 I removed the WINS settings and re-added them.
Once it registered itself, I tried to access DC1 from DC2 and got the same
error I was getting before from DC3. Now I'm really confused, cause the
addresses in WINS look perfectly fine. And, if I access DC1 by \\DC1.domain,
it works...it's just when I use \\DC1.

Does anyone have any ideas here? I'm at my witts end...
Thanks!
--Brian
 
Reply With Quote
 
 
 
 
Brian
Guest
Posts: n/a

 
      05-17-2006, 08:51 PM
To add something I just tried...I took DC2 out of the WINS databases and
cleared the NetBios cache, and it still does not work. Now I'm even more
baffeled.

Thanks,
--Brian

"Brian" wrote:

> Hi all. I've tried just about everything I can think of to resolve this, and
> need some advise. I've got 3 DCs in a mixed mode domain...DC1 is 2000, DC2
> and DC3 are 2003. If a user logs into a workstation and DC3 authenticated
> them, the user couldn't access ANlY shares on DC1, but could on DC2 and DC3.
> They'd get an error "Configuration information could not be read from the
> domain controller, either because the machine is unavailable, or access has
> been denied". However, if DC1 or DC2 authenticated the user, they could
> access everything on every server without any problems.
>
> The only difference I found between DC2 and DC3 is that DC2 wasn't listed in
> WINS database. So, on DC2 I removed the WINS settings and re-added them.
> Once it registered itself, I tried to access DC1 from DC2 and got the same
> error I was getting before from DC3. Now I'm really confused, cause the
> addresses in WINS look perfectly fine. And, if I access DC1 by \\DC1.domain,
> it works...it's just when I use \\DC1.
>
> Does anyone have any ideas here? I'm at my witts end...
> Thanks!
> --Brian

 
Reply With Quote
 
Robert L [MS-MVP]
Guest
Posts: n/a

 
      05-17-2006, 10:11 PM
Any errors in event viewer? It could be name resolution or permission issues. In this case, I would check the DNS and WINS settings first? Do you have more than one DNS and WINS servers? Basically, make sure primary DNS and 2nd DNS servers point to each other as primary and themselves as secondary if both DNS servers are in the LAN. The WINS always points to itself.



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Brian" <(E-Mail Removed)> wrote in message news:39042695-33B4-4B8B-9C85-(E-Mail Removed)...
Hi all. I've tried just about everything I can think of to resolve this, and
need some advise. I've got 3 DCs in a mixed mode domain...DC1 is 2000, DC2
and DC3 are 2003. If a user logs into a workstation and DC3 authenticated
them, the user couldn't access ANlY shares on DC1, but could on DC2 and DC3.
They'd get an error "Configuration information could not be read from the
domain controller, either because the machine is unavailable, or access has
been denied". However, if DC1 or DC2 authenticated the user, they could
access everything on every server without any problems.

The only difference I found between DC2 and DC3 is that DC2 wasn't listed in
WINS database. So, on DC2 I removed the WINS settings and re-added them.
Once it registered itself, I tried to access DC1 from DC2 and got the same
error I was getting before from DC3. Now I'm really confused, cause the
addresses in WINS look perfectly fine. And, if I access DC1 by \\DC1.domain,
it works...it's just when I use \\DC1.

Does anyone have any ideas here? I'm at my witts end...
Thanks!
--Brian
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NIC teaming problem after migration 2000 to 2003 miponte@gmail.com Windows Networking 0 08-30-2006 06:28 AM
windows 2000 vs XP networking Problem Jim Wireless Networks 4 05-06-2006 01:41 PM
Odd SBS 2003 networking problem jho Windows Networking 1 12-21-2005 03:25 AM
ME, 2000 networking problem... drum7 Windows Networking 2 05-15-2005 04:29 AM
XP and 2000 Networking Problem Kwaj Home Networking 2 05-11-2005 07:15 AM



1 2 3 4 5 6 7 8 9 10 11