Windows 2003 and NAT

I have NAt working on Windows 2003 perfectly. I have an ADSL connection connected directly to the server, and a network interface that connects to a HUB and thge rest of the network.

Its all working very well indeed.

My problem, I need to add a new wireless section to the network. Only two machine will be communicating wioth the wireless seciton, so I have no WAP and will be uising ADHOC.

If i setup NAT using EITHER the LAN OR IWrless they work fine, but I need to use BOTH. I have tried bridging the LAN and WIRELESS network connections, but then niehter work.

So I need to add another Network interface to my Remote and Routing service, which will enable my wireless device to work on the new network (see the serever and the internet).. the way I see it in simple terms, I have one public interface and two private interfaces to the internal network.

How can I make this work using NAT?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Perhaps I misunderstand your problem, but why don't you just add a wireless access point in a standard fashion and then use it for your wireless workstations? Or did you want to have those two on a segment of their own? If so, it might perhaps be easier to add a router with a WAP, and create a subnet for the 2 wireless stations.
nprignanoTechnical ArchitectCommented:
A simple SOHO wireless router costs between $50 and $75 US these days.  Definitely worth the avoided aggravation of ADHOC wireless networking.
Sure you can, but the way I've seen it work, you need to do this thru the wizard, disable the remote and accessserver and remember where is asks you for wich network interfaces conects to the internet... you should see 3 interfaces.. select your internet interface and the windows does the rest.

Depending on your settings DHCP or Static will have to setup in remote access manager properties wich interface is going to be your DHCP or range of static IP's.

It works the same way when you setup Dial-IN modem cards, the windows must setup and show all network interfaces.

KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

correct me if IM wrong but you want to use a wireless card to route to your network card, you will need Routing and Remote Access Server to route ACROSS the cards - just as if you were using dual network cards ( different subnets ).


you also want to make sure you have the wireless part setup right for ad hoc
mvwmailAuthor Commented:
Ok.. the wizard only allows one private interface to be chosen, it advises that if you have more than one private segment you need to configure DHCP.

Yes I want the wireless to be seperate.

So forgetting wireless was ever mentioned.. I have one public interface, and TWO privae interfaces both which need NAT.

My RRAS shows both of these interfaces, but only one works, the other, any workstatsion just sit there for ages and finally generate their own APIPA. Manually configring these workstations with a static IP does not work
      IP Routing
            NAT/Basic Firewall

Do you see both Cards
If not then you should right click and add the private interface for the NAT to work and have internet output.

also in
      Network interfaces
you should be able to see all available interfaces here exactly to way you said, but check for it in the NAT interfaces.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mvwmailAuthor Commented:
Thanks.. will check that tomorrow and get back

mvwmailAuthor Commented:
Well, not sure what is going down here.. removed and reinstalled all the networking stuff.. created a second SCOPE on dhcp with a new private address range, recreated the new wireless environment.
However I have to assign ip's manually on the clients as DHCP will not allocate them, but once manually added the machiens alk to each other ok.

I will have to go with the temporary fix, and pursade them to fork out for a proper WAP soon which I can plug into the hub

Thanks all
mvwmailAuthor Commented:
Oh, and the wireless connection was NOT in nat, once added internet wokred fine once I had the machines talking
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.