RE: RRAS/NAT connected stations can't access websites

Hello,

Thank you for your post.

There are many reasons which might cause the current issue.
To narrow down the issue, please help answer the following questions first.

1. To ensure that the connection to the internet works well, please check
whether the web page could be opened on RRAS server.

2. To ensure there aren't any route related issues, please check whether
you could ping any public IP addresses from your client PC. You could use
the external DNS Server IP address provided by ISP to do the test.

3. As you have mentioned that " Computers inside the network can ping the
LAN Adapter successfully and using NSLookup from computers behind the NAT
it is possible to resolve DNS Names to IP Addresses." Have you tried to
resolve the external web site's name to IP address? Can this be resolved
correctly?

4. How did you configure your client PCs' DNS server settings?
Did you point to the DNS server in your LAN?

More informations:
================
The following information is for your reference:

Troubleshooting NAT
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/intwork/
inae_ips_xsxh.mspx?mfr=true

The above article also apply to Windows Server 2003.

Deploying Dial-up and VPN Remote Access Servers
http://technet2.microsoft.com/windowsserver/en/library/8ff3534e-0f08-45bc-84
87-3b618bc8ad621033.mspx?mfr=true

I look forward to hearing from you soon. :)

Sincerely,
Neo Zhu,
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Thorin" <The_Mighty_Thorin@xxxxxxxxxxxxx>
| Subject: RRAS/NAT connected stations can't access websites
| Date: Sun, 1 Jun 2008 22:15:14 -0700
| Lines: 23
| Message-ID: <BE5FB8CD-0A16-475C-90CB-28AD916F5CAC@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
| X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| X-MS-CommunityGroup-PostID: {BE5FB8CD-0A16-475C-90CB-28AD916F5CAC}
| Newsgroups: microsoft.public.windows.server.networking
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:12958
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| Recently it became necessary to setup RRAS on Windows Server 2003 R2 to
| perform NAT for a small network that is being used as a testing
environment.
| The network had an existing domain controller that holds the roles for
| DHCP/DNS and Directory services. The RRAS server has just two network
| connections (WAN, LAN) and there it connects directly to the outside
world.
|
| The WAN NIC is set to:
| Public interface connected to the Internet
| Enable NAT on this interface
|
| There are no Inbound or Outbound Filters on the connection.
|
| Computers inside the network can ping the LAN Adapter successfully and
using
| NSLookup from computers behind the NAT it is possible to resolve DNS
Names
| to IP Addresses. What doesn't work is when a client tries to connect to a
| website using a browser all of the clients recieve an error that they
cannot
| display the page.
|
| Has anyone seen a document that explains setting up a simple NAT router
| using Windows Server 2003 R2?
|
| Thanks.
|
|

.

Relevant Pages
Quantcast