Can't setup winServer2003 to access Internet via network

  • Thread starter Thread starter Peter Chatterton
  • Start date Start date
P

Peter Chatterton

How do I configure winServer2003
to access the Internet over a peer-to-peer network?
This is probably not a tricky question as I'm not a
network guy, just a programmer (Java, C, C++, VBA, Assembler)

I've got a winServer2003 connected to an XP SP 3 and
the latter is the only one that accesses the internet,
directly that is; I want to give access to the winServer2003
thru the XP.

Here's the "Configure your Server" LOG:

(12/6/2005 2:28:59 PM)
Configurations for Your First Server
Static IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Preferred DNS server: 192.168.0.1
DHCP installed successfully.
This server has been successfully set up as a domain controller.
Install Active Directory and DNS
Full domain name: ChattertonConsulting.local
NetBIOS domain name: CHATTERTONCONSU <-- winServer2003
DNS installed successfully.
DNS queries will not be forwarded.
DHCP Server successfully authorized.
TAPI directory successfully set up.
An Application Naming Context was successfully set up in Active Directory on
this domain controller for use by TAPI client applications. If you later
need to demote this machine from being a domain controller, this Application
Naming Context should be removed with the TAPICFG utility. The Application
Naming Context has the following DNS name:
chatt-server.ChattertonConsulting.local.

(12/6/2005 2:41:42 PM)
Configurations for a File Server
Indexing Services started.
File Server Management added under Start/Programs/Administrative Tools.
This server is configured as a file server.

(12/6/2005 8:43:41 PM)
Configurations for an Application Server
IIS installed successfully.


I'm also having a problem setting up a firewall.
The help files say to configure Basic Firewall:
Open Routing and Remote Access.
In the console tree, click NAT/Basic Firewall.
Routing and Remote Access
ServerName
IP Routing
NAT/Basic Firewall

In mine, rt-clicking ServerName does show IP as a tab under Properties,
but there's nothing there about fire walls.

Hope you can help,
Peter.
 
In
Peter Chatterton said:
How do I configure winServer2003
to access the Internet over a peer-to-peer network?
This is probably not a tricky question as I'm not a
network guy, just a programmer (Java, C, C++, VBA, Assembler)

I've got a winServer2003 connected to an XP SP 3 and
the latter is the only one that accesses the internet,
directly that is; I want to give access to the winServer2003
thru the XP.

Here's the "Configure your Server" LOG:

(12/6/2005 2:28:59 PM)
Configurations for Your First Server
Static IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Preferred DNS server: 192.168.0.1
DHCP installed successfully.
This server has been successfully set up as a domain controller.
Install Active Directory and DNS
Full domain name: ChattertonConsulting.local
NetBIOS domain name: CHATTERTONCONSU <-- winServer2003
DNS installed successfully.
DNS queries will not be forwarded.
DHCP Server successfully authorized.
TAPI directory successfully set up.
An Application Naming Context was successfully set up in Active
Directory on this domain controller for use by TAPI client
applications. If you later need to demote this machine from being a
domain controller, this Application Naming Context should be removed
with the TAPICFG utility. The Application Naming Context has the
following DNS name: chatt-server.ChattertonConsulting.local.

(12/6/2005 2:41:42 PM)
Configurations for a File Server
Indexing Services started.
File Server Management added under Start/Programs/Administrative
Tools. This server is configured as a file server.

(12/6/2005 8:43:41 PM)
Configurations for an Application Server
IIS installed successfully.


I'm also having a problem setting up a firewall.
The help files say to configure Basic Firewall:
Open Routing and Remote Access.
In the console tree, click NAT/Basic Firewall.
Routing and Remote Access
ServerName
IP Routing
NAT/Basic Firewall

In mine, rt-clicking ServerName does show IP as a tab under
Properties, but there's nothing there about fire walls.

Hope you can help,
Peter.
Click to expand...

Well, you're not using a peer to peer network if you have Active Directory,
which you evidently do.

Don't use WinXP ICS for this purpose (hell, even without a domain I don't
like ICS). Get yourself a decent broadband router/firewall that can do NAT,
set it up with a static IP on your LAN, and point the server/workstations at
that IP as the default gateway.
 
Back
Top