I am the network admin of a local business. Let me describe a little bit of the topology of the setup. There are 3 buildings. The first building is where the internet connection comes in. The second building is the main office with 10-20 PCs and also houses the server, the switch, a WAP, and a wireless radio, that makes a point to point bridge to the first building. The whole network is on a 172.20.7.x network. The server is a 2K3 SBS. It is acting as the PDC, a DHCP server, it is sharing an application to select users, it will soon be running ISA and Exchange most likely in the near future. There is now a third building where a group of PCs needs to be installed. It is connected the first building with a Cat5 run terminated into a switch and the end in the first building is terminated into a the wireless radio's of the PtP link's second Ethernet port. Ok, now the problem: I can not join the domain from this building. I receive DHCP from the server, I can ping it by DNS. I can browse shared directories on the server, I can access every service that is configured to be used, but actually joining the domain. I get the error message basically stating that it could not find the domain controller. Check to make sure DNS is configured properly. It was because a machine joined on the same side of the wireless bridge as the server, that same day. Any ideas? Maybe where to start? Communication is clearly open between the PC and the server The server doesn't know that the frames coming to it originated from the wire or wireless. In this case it originated on a wire then wirelessly then back to the wire. Thanks for reading and I appreciate any input! Have a great weekend

Did you check the DNS address on the client you were trying to join with? If not do so, if it's not the IP address of your DC, that's the issue. If it is, post back and we'll see if we can't help you figure it out. Oh, one more thing. Try rejoining the domain as is and write the error message down verbatim. Saying "an error message saying something like....." isn't as helpful as the exact error message. Once you have the exact error message, begin troubleshooting it by researching it on microsoft's knowledge base and on google.

Odds are you need to add the remote ip subnet in Active Directory Sites and Services, then add the subnet. Are you ready for where Microsoft wants you to go today?