Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

connect part wired to part wireless lan

Status
Not open for further replies.

jatkinson

Technical User
Nov 14, 2001
406
GB
Hi all,

Any pointers on how I can connect part of my LAN which is wired to a wireless part?

Specifically, all my devices connect to a wireless AP, including one of my servers (DC) in my home 'office' room, the other server is a DC too and is wired via a switch to the DC with the wireless card. I was hoping therefore I could bridge the wired lan and wirelesss connections together so the wireless devices could reach the wired DC. With me so far?

Anyway, I can route from the DC (with wireless) to the wireless devices with the bridge setup, and it only works when they're unbridged if the wired lan connection is disabled.

Do I need to put the IP addresses on different subnets, make all gateway addresses the same etc or something else

Any advice?

Cheers,
 
I'm a little confused about your configuration. I had to do a quick learn about bridging a couple months ago. A few devices offer WDS (bridging options). I used it however, all my equipment connects to the same DC and has the same IP subnet. It seems to work well despite my configuration...(I've got a large campus and I'm pointing some fo the signals through a 138KV electrical switchyard and it works.)

Again, I'm confused about your configuartion but you might consider changing the subnet mask to make sure everything can talk. If you've setup class C addressing for each segment, you might need to use a 255.255.0.0 subnet mask to eliminate the need for a router.


mike
 
It sounds pretty simple to me. Windows 2000 and 2003 Server both ship with NAT and Routing capabilities. Whether or not your wired and wireless are on the same network is not relevant (since you can peform routing via either of your DC's). If your goal is simply to provide wireless access to your DC, you're already half way there. However, from a security perspective, I would advise against having a wireless NIC hanging out of your domain controller. Just curious, why do you need a direct wireless connection to your DC?

CISSP,ISC2 Affiliate & Instructor, MCT, MCSE2K/2K3, MCSA, CEH, Security+, Network+, CTT+, A+
 
Simply because they are in a different room to my Client devices and I cannot cable through the rooms due to layout issues.
 
If that be the case, have an AP that is hard wired to the DC (via cat5) then bridge that AP with another one on the other side of the walls.

CISSP,ISC2 Affiliate & Instructor, MCT, MCSE2K/2K3, MCSA, CEH, Security+, Network+, CTT+, A+
 
Yeah, that is what I'm going to do, I was just looking to find a solution with the kit I had available at the time.

Cheers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top