Cannot connect to internet behind NAT

I am a total noob to this so bear with me. I have recently installed 2003
Server on a machine and it has an external wireless connection to the
internet. It also has a wired internal NIC that provides DHCP to a switch.
On the computer connected to the switch I am unable to access the internet.
However, I can access the shares and whatnot on the server. I have the XP
machine joined to my domain and it is in the DHCP Users group. It gets an IP
fine and seems to have DNS working fine as well(when I ping google.com it
resolves the hostname to IP but then I get "Request timed out). I don't know
where to start on figuring out how one day I just couldn't get on the
internet. It seems as if the 2003 machine is denying me access to the
internet. Please help a noob out. Thanks in advance. Let me know if I need
to be more specific about the configs on my internal and external interfaces.

"Steven Platt" wrote in message
news:85E9860E-1BB3-49AF-A2A1-(E-Mail Removed)...
:I am a total noob to this so bear with me. I have recently installed 2003
: Server on a machine and it has an external wireless connection to the
: internet. It also has a wired internal NIC that provides DHCP to a
switch.
: On the computer connected to the switch I am unable to access the
internet.
: However, I can access the shares and whatnot on the server. I have the XP
: machine joined to my domain and it is in the DHCP Users group. It gets an
IP
: fine and seems to have DNS working fine as well(when I ping google.com it
: resolves the hostname to IP but then I get "Request timed out). I don't
know
: where to start on figuring out how one day I just couldn't get on the
: internet. It seems as if the 2003 machine is denying me access to the
: internet. Please help a noob out. Thanks in advance. Let me know if I
need
: to be more specific about the configs on my internal and external
interfaces.

What is an external wireless connection to the Internet? NICs don't provide
DHCP to switches.

Do you have a router that supports wired and wireless connections, a 2K3
server and a workstation?
Is the router connected to the switch?
Hopefully you're not saying the server connects wirelessly to the router and
wired to a switch which only has the server and a workstation connected.

This: Internet -> [Router -> wireless to Server][Router -> wired to
Switch] -> Workstation and Server also has wired connection to switch
or
That: Internet -> Router -> [wireless to Server] -> Server wired to
switch -> Workstation

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/service...p?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default...b;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default...b;EN-US;291382

Thank you for the quick response. In your terms I have "That."

Internet --> Router(wireless) --> Server 2003(External NIC is wireless) -->
Server 2003(Internal NIC wired) --> switch --> Workstation(Windows XP)

Does this make sense? It seems like a crazy/stupid setup. But I am
experimenting. I guess what I meant was that the Server 2003 provides DHCP
to the XP machine. I have the internet connection from the router wirelessly
to the server then I have the server wired to the switch to which the XP
machine is also connected wired. The external IP of my server is
192.168.1.100 and the internal is 192.168.0.1. The XP machine is getting IPs
like 192.168.0.100 and I have the DNS set as the internal of the
server(192.168.0.1). In 'computers' under 'Active Directory Users and
Computers' on the server it has the XP Machine listed. Any ideas on what is
preventing this machine from accessing the internet? Thank you so much
Roland.

-Steven-
"Roland Hall" wrote:

> "Steven Platt" wrote in message
> news:85E9860E-1BB3-49AF-A2A1-(E-Mail Removed)...
> :I am a total noob to this so bear with me. I have recently installed 2003
> : Server on a machine and it has an external wireless connection to the
> : internet. It also has a wired internal NIC that provides DHCP to a
> switch.
> : On the computer connected to the switch I am unable to access the
> internet.
> : However, I can access the shares and whatnot on the server. I have the XP
> : machine joined to my domain and it is in the DHCP Users group. It gets an
> IP
> : fine and seems to have DNS working fine as well(when I ping google.com it
> : resolves the hostname to IP but then I get "Request timed out). I don't
> know
> : where to start on figuring out how one day I just couldn't get on the
> : internet. It seems as if the 2003 machine is denying me access to the
> : internet. Please help a noob out. Thanks in advance. Let me know if I
> need
> : to be more specific about the configs on my internal and external
> interfaces.
>
> What is an external wireless connection to the Internet? NICs don't provide
> DHCP to switches.
>
> Do you have a router that supports wired and wireless connections, a 2K3
> server and a workstation?
> Is the router connected to the switch?
> Hopefully you're not saying the server connects wirelessly to the router and
> wired to a switch which only has the server and a workstation connected.
>
> This: Internet -> [Router -> wireless to Server][Router -> wired to
> Switch] -> Workstation and Server also has wired connection to switch
> or
> That: Internet -> Router -> [wireless to Server] -> Server wired to
> switch -> Workstation
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/service...p?fr=0&sd=tech
> How-to: Windows 2000 DNS:
> http://support.microsoft.com/default...b;EN-US;308201
> FAQ W2K/2K3 DNS:
> http://support.microsoft.com/default...b;EN-US;291382
>
>
>

Hi Steven...

Thanks for responding...

"Steven Platt" wrote in message
news:AB3FC6E3-E07C-46AE-9868-(E-Mail Removed)...
: Thank you for the quick response. In your terms I have "That."

(O:=

: Internet --> Router(wireless) --> Server 2003(External NIC is
wireless) -->
: Server 2003(Internal NIC wired) --> switch --> Workstation(Windows XP)

It makes sense what you have but it's not necessary to do it that way. No
reason to try to route through the server, which would then require ICS or
RRAS.

: Does this make sense? It seems like a crazy/stupid setup. But I am
: experimenting. I guess what I meant was that the Server 2003 provides
DHCP
: to the XP machine. I have the internet connection from the router
wirelessly
: to the server then I have the server wired to the switch to which the XP
: machine is also connected wired. The external IP of my server is
: 192.168.1.100 and the internal is 192.168.0.1. The XP machine is getting
IPs
: like 192.168.0.100 and I have the DNS set as the internal of the
: server(192.168.0.1). In 'computers' under 'Active Directory Users and
: Computers' on the server it has the XP Machine listed. Any ideas on what
is
: preventing this machine from accessing the internet? Thank you so much
: Roland.

You're welcome and yes. I'm going to describe a simple setup but it depends
on the location of all devices. If you are connecting to the router from
the server wirelessly because you cannot reach it by wire, then we'll have
to make a different plan. If not, then we'll nix the switch and the
wireless connection since 100Mbps is faster across the wire than 54
(actually 44) or 11 is wirelessly.

I forgot to ask which router but I will assume a SOHO router (Belkin,
Linksys, NetGear, etc.) with a 4 port switch builtin.

If the server gets it's address [wirelessly] from DHCP on the router,
disable DHCP on the router. If DHCP is already disabled on the router, skip
this step.
Connect the server's internal NIC to a port on the router and do the same
for the workstation.
Disable or remove the wireless NIC on the server.
Change the server's internal NIC's IP address to 192.168.1.2 (assuming
router is 192.168.1.1 or at least not .2.)
If required, ipconfig /release and ipconfig /renew on the workstation to get
a new IP address on the 192.168.1.0 network.
As long as the router is not blocking anything you should be able to get
out.

If you have issues, let me know what the error message is exactly and/or
what's happening and we'll go from there.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/service...p?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default...b;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default...b;EN-US;291382

Roland,

You hit the nail on the head. I can't reach the router physically so I am
forced to get an IP from it wirelessly. Then I decided to implement NAT
since I had an onboard NIC on both my computers'. I know I could have gone
with ICS but I didn't have any crossover cable handy; but I did have a
switch, go figure. Also the switch comes in handy when I have to do work on
other computers because I can just plug them directly into the switch and
get an IP from Server 2003. I like the setup I have for what I do. It
works wonders and is so convenient with my KVM switch being right there. I
am just wondering what happened overnight that caused it to stop working. I
will tell you what I was doing and maybe that will help narrow down what
_could_ be the problem. I was trying to u/l things to my website(not
anything internal). And I kept getting errors. I would tell you the error
but I can't even get on the internet anymore with that computer Anyways,
I was messing with the external and internal NIC in RRAS. In particular I
was messing with the "Routing and Remote Access" --> "MyServer" -- "IP
Routing" --> "General" and "NAT/Basic Firewall" tabs. I thought I put
everything back to the way it was, but obviously I didn't. I don't have any
inbound nor outbound filters on either of the interfaces(internal and
external). I have even disabled the "Basic Firewall" option for the
external interface(Wireless NIC). Maybe that can help you a little on what
I am experiencing. Like I said, I am a noob so take it easy on me.
Thanks again, man, for all the good information. You have made my first
newsgroup experience a pleasant one.

-Steven-


"Roland Hall" <nobody@nowhere> wrote in message
news:(E-Mail Removed)...
> Hi Steven...
>
> Thanks for responding...
>
> "Steven Platt" wrote in message
> news:AB3FC6E3-E07C-46AE-9868-(E-Mail Removed)...
> : Thank you for the quick response. In your terms I have "That."
>
> (O:=
>
> : Internet --> Router(wireless) --> Server 2003(External NIC is
> wireless) -->
> : Server 2003(Internal NIC wired) --> switch --> Workstation(Windows XP)
>
> It makes sense what you have but it's not necessary to do it that way. No
> reason to try to route through the server, which would then require ICS or
> RRAS.
>
> : Does this make sense? It seems like a crazy/stupid setup. But I am
> : experimenting. I guess what I meant was that the Server 2003 provides
> DHCP
> : to the XP machine. I have the internet connection from the router
> wirelessly
> : to the server then I have the server wired to the switch to which the XP
> : machine is also connected wired. The external IP of my server is
> : 192.168.1.100 and the internal is 192.168.0.1. The XP machine is
getting
> IPs
> : like 192.168.0.100 and I have the DNS set as the internal of the
> : server(192.168.0.1). In 'computers' under 'Active Directory Users and
> : Computers' on the server it has the XP Machine listed. Any ideas on
what
> is
> : preventing this machine from accessing the internet? Thank you so much
> : Roland.
>
> You're welcome and yes. I'm going to describe a simple setup but it
depends
> on the location of all devices. If you are connecting to the router from
> the server wirelessly because you cannot reach it by wire, then we'll have
> to make a different plan. If not, then we'll nix the switch and the
> wireless connection since 100Mbps is faster across the wire than 54
> (actually 44) or 11 is wirelessly.
>
> I forgot to ask which router but I will assume a SOHO router (Belkin,
> Linksys, NetGear, etc.) with a 4 port switch builtin.
>
> If the server gets it's address [wirelessly] from DHCP on the router,
> disable DHCP on the router. If DHCP is already disabled on the router,
skip
> this step.
> Connect the server's internal NIC to a port on the router and do the same
> for the workstation.
> Disable or remove the wireless NIC on the server.
> Change the server's internal NIC's IP address to 192.168.1.2 (assuming
> router is 192.168.1.1 or at least not .2.)
> If required, ipconfig /release and ipconfig /renew on the workstation to
get
> a new IP address on the 192.168.1.0 network.
> As long as the router is not blocking anything you should be able to get
> out.
>
> If you have issues, let me know what the error message is exactly and/or
> what's happening and we'll go from there.
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/service...p?fr=0&sd=tech
> How-to: Windows 2000 DNS:
> http://support.microsoft.com/default...b;EN-US;308201
> FAQ W2K/2K3 DNS:
> http://support.microsoft.com/default...b;EN-US;291382
>
>

"Steven Platt" wrote in message
news:(E-Mail Removed)...
: Roland,
:
: You hit the nail on the head. I can't reach the router physically so I am
: forced to get an IP from it wirelessly. Then I decided to implement NAT
: since I had an onboard NIC on both my computers'. I know I could have
gone
: with ICS but I didn't have any crossover cable handy; but I did have a
: switch, go figure. Also the switch comes in handy when I have to do work
on
: other computers because I can just plug them directly into the switch and
: get an IP from Server 2003. I like the setup I have for what I do. It
: works wonders and is so convenient with my KVM switch being right there.
I
: am just wondering what happened overnight that caused it to stop working.
I
: will tell you what I was doing and maybe that will help narrow down what
: _could_ be the problem. I was trying to u/l things to my website(not
: anything internal). And I kept getting errors. I would tell you the
error
: but I can't even get on the internet anymore with that computer
Anyways,
: I was messing with the external and internal NIC in RRAS. In particular I
: was messing with the "Routing and Remote Access" --> "MyServer" -- "IP
: Routing" --> "General" and "NAT/Basic Firewall" tabs. I thought I put
: everything back to the way it was, but obviously I didn't. I don't have
any
: inbound nor outbound filters on either of the interfaces(internal and
: external). I have even disabled the "Basic Firewall" option for the
: external interface(Wireless NIC). Maybe that can help you a little on
what
: I am experiencing. Like I said, I am a noob so take it easy on me.
: Thanks again, man, for all the good information. You have made my first
: newsgroup experience a pleasant one.

Hi Steven...

Sorry for the delay. I was in seminars all day.

These two links may be helpful in narrowing down the problem.
http://www.windowsnetworking.com/art...iguration.html

This one, look at the last question:
http://www.chicagotech.net/nat.htm

If that is not clear enough, can you show the IPCONFIG /ALL on the server
and the workstation?

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/service...p?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default...b;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default...b;EN-US;291382