Hi guys
I'm having a difficult time trying to get this right, hopefully someone can assist me.
I have a computer with Server 2008 R2 that has a WiFi NIC and a LAN NIC.
The WiFi is connecting to a wireless router that has unrestricted internet access, and the LAN is connected to a wired router allowing a number of clients to connect.
I want for the clients on the LAN to be able to access the internet that is on the wireless.
The issue I am having is that the LAN clients just cannot get access to internet, i have tried using RIP and NAT, that did work initially but for some reason it did not survive a reboot of the server and then I could never get it working again.
I do have DHCP installed to provide IP addresses to the LAN clients, and I have DNS installed which is using Google's public DNS (8.8.8.8)
A little background info on my network setup:
Wireless router supplying internet has a gateway address of 192.168.1.1
WiFi NIC on server has a static IP 192.168.1.2
LAN NIC on server has static IP 192.168.0.10 and I have turned DHCP off on the router as i want the server to allocate IPs
If anyone could shed some light on how to set this up properly I would really appreciate it.
Oh and I'm using a workgroup setup, not domain
Thank you
Server 2008 R2 routing
- hamin_aus
- Forum Moderator
- Posts: 18363
- Joined: 28 Aug 2003, 02:00
- Processor: Intel i7 3770K
- Motherboard: GA-Z77X-UP4 TH
- Graphics card: Galax GTX1080
- Memory: 32GB G.Skill Ripjaws
- Location: Where beer does flow and men chunder
- Contact:
Re: Server 2008 R2 routing
I would also say if you have got NAT to work once keep trying to get it working again.
It sounds like RRAS and NAT are exactly what you need to do the job.
If NAT worked until a reboot - what changed after the reboot? More to the point, what on the server and/or router did you change in between getting NAT to work and doing a reboot?
If all else fails try setup ICS (unless you have an SBS server) it's not as good as NAT but it's better than nothing
It sounds like RRAS and NAT are exactly what you need to do the job.
If NAT worked until a reboot - what changed after the reboot? More to the point, what on the server and/or router did you change in between getting NAT to work and doing a reboot?
If all else fails try setup ICS (unless you have an SBS server) it's not as good as NAT but it's better than nothing
-
- Registered User
- Posts: 14338
- Joined: 04 Sep 2004, 02:00
- Processor: i386DX Sooper
- Motherboard: A blue one
- Graphics card: A red one
- Memory: Hard drive
- Location: On a Möbius strip
- Contact:
Re: Server 2008 R2 routing
MuPp3t33r forgot to reply here, but his issue has been solved.
If I weren't insane: I couldn't be so brilliant! - The Joker
Re: Server 2008 R2 routing
My apologies, I did forget to reply. Issue was resolved but through an alternate method.
As far as anything changing before and after rebooting, nothing changed at all.
But anyway I instead bridged the two adapters, but DHCP wouldn't give me the correct scope I wanted so I had to change the gateway address on my LAN router and adjust the DHCP scope. but it seems to be working now...
As far as anything changing before and after rebooting, nothing changed at all.
But anyway I instead bridged the two adapters, but DHCP wouldn't give me the correct scope I wanted so I had to change the gateway address on my LAN router and adjust the DHCP scope. but it seems to be working now...
-
- Registered User
- Posts: 26022
- Joined: 13 May 2004, 02:00
- Location: Getting there...
- Contact:
Re: Server 2008 R2 routing
Stop apologising and start spamming the other threads...
MOOD - Thirsty
A surprising amount of modern pseudoscience is coming out of the environmental sector. Perhaps it should not be so surprising given that environmentalism is political rather than scientific.
Timothy Casey
A surprising amount of modern pseudoscience is coming out of the environmental sector. Perhaps it should not be so surprising given that environmentalism is political rather than scientific.
Timothy Casey