Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 369
  • Last Modified:

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?
0
mvwmail
Asked:
mvwmail
  • 4
  • 2
  • 2
  • +2
1 Solution
 
ridCommented:
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.
/RID
0
 
nprignanoTechnical ArchitectCommented:
A simple SOHO wireless router costs between $50 and $75 US these days.  Definitely worth the avoided aggravation of ADHOC wireless networking.
0
 
CKWTCommented:
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.

0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Craig_200XCommented:
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 ).

(http://support.microsoft.com/kb/321516/en-us)


0
 
Craig_200XCommented:
you also want to make sure you have the wireless part setup right for ad hoc

http://www.microsoft.com/windowsxp/using/networking/expert/bowman_02april08.mspx
0
 
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
0
 
CKWTCommented:
in
servername(local)
      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
servername(local)
      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.


CKWT
0
 
mvwmailAuthor Commented:
Thanks.. will check that tomorrow and get back

Morgan
0
 
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
0
 
mvwmailAuthor Commented:
Oh, and the wireless connection was NOT in nat, once added internet wokred fine once I had the machines talking
0

Featured Post

The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

  • 4
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now