Expert: Wireless / Wired Win 2k network

[gbhachu]

Hi,
This problem has been on my mind for many months now, and i'm at a point where i'm about to just give up.

Let me set the scene:

Four machines:
1. Desktop Win2K Server with 1 56K modem + 1 100Mbps NIC
2. Desktop Win2K Server with 1 100Mbps NIC + 1 11Mbps Wireless NIC
3. Laptop Win2K Prof with 1 100Mbps NIC
4. Laptop Win2K Prof with 1 11Mbps Wireless NIC

Other hardware:
1. Fast Ethernet 100Mbps switch
2. many crossover network cables + many straight thru network cables

Note: I do NOT have a Wireless Access Point (AP)

Here's what I would like to do:
1. Want machine 1 to be able to dial to internet over the modem using dial-demand. This could act as DHCP/DNS/Web server etc.
2. Want all other machines to be able to talk to each other.

Questions:
1. What's the best way to do what I want within my hardware/software restriction?

2. Want the wireless LAN to be able to talk to wired machines and internet.

3. Can't use ICS correct? So have to use NAT? How to do this for two mixed mode mcahines?

4. Is it possible to do at all without an AP?

5. Lets say I want to use 192.168.0.0 for wired and 192.168.?.0 for wireless.

This is the configuration I had in mind:

|*|
| WIRELESS NIC 1
INTERNET---------------------
| Machine 1 |
-------------
| WIRED NIC 1
|
|
\ |
\ |
\------------- -------------
| Switch | WIRED NIC 3 | Machine 3 |
--------------------------------------------------
|
|
|
------------- WIRED NIC 2
| Machine 2 |
-------------

|*|
|
-------------
| Machine 4 |
-------------

So, what we have here is Machine 1 with both a wireless nic and a wired nic and a modem - 3 interfaces. Machine 4 (the laptop) is free to roam around (the garden). The switch can have a couple more wired machines if necessary.

I've read tens and tens of tutorials on WIN2K server/DHCP/DNS/RRAS routing/NAT/etc etc list goes on. Has anyone done this? I really require step-by-step instructions.....?

Please feel free to reply with ANY suggestions.

Many many thanks
Gurps

 

[gbhachu]

Hi me again!

Do you think I need to have the wired and wireless network on separate LANs first. Say

Server-wired NIC-----------wired NIC-Client

Server-wireless NIC-----------wireless NIC-Client


The top LAN has DHCP with 192.168.1.0 subnet
The bottom LAN has DHCP with 192.168.2.0 subnet

Now I guess the challenge is how does the wired talk to the wireless? WITHOUT the use of an AP? I've heard people have done this in LINUX using "IP forwarding/masquerading" (i'm not too hot with LINUX terms).

Is it called bridging? Routing? I'm VERY confused.

Thanks

 

[gbhachu]

More info:

With 2 wireless NICs you use them in something called "Ad-Hoc" mode. I think this is basically like peer 2 peer. Is this the equivalent of having a crossover cable between two wired NICs? Also equivalent of having 2 WIred NICs going into the same hub/switch ??

Cheers!

 

[gbhachu]

what about only 1 machine acting as the DHCP server with 2 "scopes". Well how do I do that? Is that a good idea??

G.

 

[gbhachu]

What this layout:

http://www.raubacapeu.net/people/yves/2000/10/26-network

what's the Windows equivalent in Win 2K Server to do what this guy's achieved?