Re: WS2003, XP Clients, and Network Setup Help

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: gregoryt (gregoryt_at_discussions.microsoft.com)
Date: 11/29/04


Date: Mon, 29 Nov 2004 06:19:02 -0800


Thanks for your help Bill. I'm going to try setting up the network the way
you suggested.

Greg

"Bill Grant" wrote:

> This is really a bit of a can of worms. New problems may just keep
> popping up. AD plus NAT plus PPPoE plus Macs!
>
> If you must use your DC as the Internet router, you certainly should be
> using RRAS and NAT (not bridging). For AD to work, all the AD clients should
> be using the 10.0.0 IP addresses you used to set up AD, and they should be
> using the local (10.0.0.x ) DNS server.
>
> The server has an Internet connection using PPPoE. With W2k3 this can be
> set up within RRAS. The PPPoE interface becomes your "public" interface for
> NAT. The 10.0.0.x interface of the server becomes the private interface in
> NAT. NAT allows the LAN clients to share the server's Internet connection.
>
> The LAN clients get their config from DHCP on your server. They should
> get an IP in the 10.0.0.0 subnet and a default gateway and DNS setting of
> your server's 10.0.0 address. You will need to modify your local DNS so
> that it forwards requests to a public DNS server (such as your ISP's DNS).
>
> When you have AD and NAT working, you can experiment with VPN. Enable
> remote access in RRAS and try making a VPN connection from a LAN client.
> (VPN will work over the local LAN). This will let you debug the VPN config
> on your server locally.
>
> Because your RRAS server is a DC, you may get name resolution problems
> when a remote access client connects. See KB 292822 .
>
> When this works, you can try connecting from a remote client. Your
> no-ip.com address should point you to the server's current public IP. If it
> works internally, it should work over the Internet.
>
> "gregory_t" <gregoryt@discussions.microsoft.com> wrote in message
> news:A74B5BAE-0361-412C-8BBE-505762F673B0@microsoft.com...
> > Hi all. I'm hoping someone can help me.
> >
> > Here's my current setup. I have an IBM xServer running Windows 2003 Std
> > Edition. I have DHCP and AD setup. Initially, I set up DHCP's scope to
> > 10.0.0.10 - 10.0.0.25. I have 9 XP clients, and 3 eMacs so far in the
> > lab.
> > There are two NICs in the server. One for the private LAN, and the other
> > is
> > directly connected to the DSL modem. By browsing to 192.168.2.1 on the
> > Server, I'm able to access my ISP's (Bell Sympatico) setup page and enter
> > all
> > the PPPoE info I need to connect. Once this is entered, I can browse the
> > Internet on the server. However, I wasn't able to successfully access the
> > Internet form the XP clients. The only way I can get Internet access on
> > the
> > XP machines and the eMacs is by bridiging the two network cards.
> >
> > Once I bridge the connections, all the XP machines and the eMacs get an IP
> > from the server and the IPs of those are 192.168.2.10 - 192.168.2.25. On
> > the
> > server, I setup a no-ip.com account to inform me of the IP whenever it
> > changes so I can always point to the lab from a remote connection, but it
> > will also point back to the ISP setup page, and not to the server.
> > Whenever
> > I try to connect through a VPN connection, I get error 800 and have no
> > clue
> > where to go from here.
> >
> > I'd like to get VPN access to the machines but I don't know where to go
> > from
> > here. Is there a better way to get Internet access to the machines? Do I
> > need to set up routing and remote access on the server to get a VPN
> > connection? How can I open the proper ports so that my no-ip.com will
> > point
> > and access a VPN session on the server?
> >
> > Thanks for reading guys.
> >
> > G.
> >
>
>
>



Relevant Pages

  • Re: EBS 2008, TMG and external firewall. Dont want double NAT
    ... This is done because Exchange is bound to the internal interface and leaves the external interface to be *completely* controlled by TMG...a good security guideline by the way. ... If you are disabling NAT then you'll need to change this from a publishing rule to an access rule, but it should still work fine. ... The first is an access rule allows traffic from the internal IP to the external interface and to the messaging server ... One of the default rules is an "internet access for all users" that allows http and https by default. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Issue
    ... 317025 You Cannot Connect to the Internet After You Connect to a VPN Server ... | first done with a standard usb broadband modem on XP Professional. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sometimes it works sometimes it doesnt (VPN data issues)
    ... NIC1 "Internet" is set to ... (the IP of the external firewall) and the DNS is set to ... A connection between the VPN server and the VPN client xxx.xxx.xxx.xxx ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Error code 800 HELP!
    ... Can you visit Internet and OWA on SBS server? ... Just one PC get error code 800 connecting VPN connecting to SBS? ...
    (microsoft.public.windows.server.sbs)
  • RE: Sharing VPN client connection
    ... as a VPN server, configure the internal clients to connect the remote ... office by VPN connection and then access to the Internet from the Remote ... Enable internal clients to access the Internet. ... On the server, go to My Network Places, click New Connection Wizard. ...
    (microsoft.public.windows.server.sbs)