Click here for important information about

Connectivity Problem Win Server 2008 2 NIC

Microsoft Windows server 2008 enterprise
October 18, 2010 at 16:48:36
Specs: Windows server 2008
Appreciate any help with the "missing link" to complete client connectivity on Windows Server 2008!

We just installed Windows Server 2008.
Under Server 2003 we had a working network that was configured:
internet<>NIC-WAN<>Server<>NIC-LAN<>Switch<>PCs/printers/other networked devices

Here's where we are:
- Server is connected to the internet (Wan card)
-Client pcs connected through switch to server are getting IPs from server through LAN card but have no internet connection.

We have a single server, no domains.
NIC setup:
WAN Card: ISP assigned Static IP, Gateway, SNet & DNS numbers
LAN Card: TCP/IP is configured with Static IP that is the 1st in our selected scope range,
Subnet =, DNS # is the same as the IP

Before the upgrade this configuration worked without a hitch.
With, 2008 we can't figure out the missing link:

Any thoughts as to what step(s) we're missing?

See More: Connectivity Problem Win Server 2008 2 NIC

October 18, 2010 at 18:13:21
No mention of RRAS. What were you using previously? Lan nic has gateway blank?

Report •

October 18, 2010 at 19:03:40
I posted this and THEN we found the passage to Routing by adding Network Policy and Access Role. Thank you we are are set and all is good (yes began with blank gateway for Lan nic)

Wanderer, your answers to much earlier questions here were a big help in sussing this out. Thank you especially for that.

BTW, I realized Network Policy and Access after I found this tutorial:

It seems so simple in retrospect.


Report •
Related Solutions

Ask Question