I think the confusion is resulting from the fact that in Windows NAT
configurations the non-LAN NIC is always referred to as the "public" NIC.
This is so even when the IP of the "public" NIC is not a public IP:
1. If your server's public NIC is connected to the LAN port of a NAT
router, and the router's WAN/Internet port is connected to a modem or other
Internet connection device; then the public NIC will/must have a private IP.
AND NAT must be enabled on the router.
2. In order for LAN clients to access the Internet, the subnet for the
public NIC must be different from the subnet for the LAN NIC. The default
for many routers is 192.168.1.x - since this is the same as your LAN subnet,
this may be part of your problem. Once you have different subnets
configured you can:
a. Enable NAT on the server - this 'should' work, but sometimes a double
NAT configuration does not work well or at all; or
b. Simply enable routing on the server. However, for straight routing you
will need to configure a static route on the router. This route points to
the IP of the server's public NIC as a gateway for packets destined for the
192.168.1.x network. The way you configure a static route is device
dependent - consult your manual. Some low end NAT routers do not support
this feature.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"john" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> The server has been configured as a router for both LAN and Demand-dial
> routing.The two NICs are both enabled. I turned NAT off at the router
> and turned it on at the server.I still can't ping the router from the
> workstation. I can ping the public IP on the public NIC though, just
> not the gateway.
> Robert L [MS-MVP] wrote:
> > if you enabled the two NICs and NAT on the server, you need to make the
server as a router to route the traffic. check this link
> >
> > How to setup vpn on 2003 as router How to setup VPN and NAT on Windows
Server 2003 as a router. Pre-requirement: ... Note: because this server is
also a router it is better to enable NAT. ...
> > www.howtonetworking.com/VPN/2003vpn1.htm
> >
> > However, in the most cases, you don't need two NICs and enable NAT
since you already have a router.
> >
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
> > "john" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> > I can ping the router only from the server. The workstations can't
ping
> > it.
> > Robert L [MS-MVP] wrote:
> > > could be the routing issue. can you ping the router? if yes, can you
ping the a public IP?
> > >
> > > Bob Lin, MS-MVP, MCSE & CNE
> > > Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
> > > How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
> > > "john" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> > > My server is multi-homed. One NIC is connected to the LAN and the
other
> > > to the Internet. All workstations have private IPs and the server
has
> > > a public IP. All workstations are connected to a switch.All
computers
> > > including the server can see each other. NAT is on at the router.
My
> > > problem is that the workstations can't browse the Internet, but
the
> > > server can, with no problem.Would really appreciate some help on
this.
>
Similar Threads
Linear Mode
