Networking Forums

Networking Forums > Computer Networking > Windows Networking > Server 2003 routing

Reply
Thread Tools Display Modes

Server 2003 routing

 
 
Daryl
Guest
Posts: n/a

 
      11-01-2006, 02:47 PM
We have a classroom environment as follows:

In a lab we will have 10 stand alone 2003 servers with AD installed and 10
Windows XP machines. We have an 11th stand alone "instructor" 2003 server.

All of the machines are connected to a university network through which they
have internet access, DHCP addresses, and other resources.

Method 1: If we use University settings for our DNS servers and default
Gateways, traffic gets routed through "corporate" firewalls and we have
difficulty with joining domains on our classroom servers, logins take
forever, accessing shares doesn't allways work, etc. We have been told this
is an issue with the organizations routing and that there is no easy fix
except to do use Method 2.

Method 2: If we "hard" code the default gateway and DNS server (on both the
2003 servers and XP workstations) to the IP address of "instructor" 2003
server everything seems to work better. Logins are fast, joining domains
works, etc. The only downside is that we can no longer access the Internet
to download drivers, patches and updates, etc.

Question 1: What is the best/easist way (using Method 2) to have the
"Instructor" 2003 server route traffic to the Internet (i.e. pass through any
traffic it does not recognize to the "corporate" default gateway) without
effecting any other computers on the university network?

Question 2: Any other ideas or suggestions as to how to make our lab
situation work?

Thanks for any help you can provide.



 
Reply With Quote
 
 
 
 
Robert L [MVP - Networking]
Guest
Posts: n/a

 
      11-01-2006, 05:33 PM
Assuming there are two subnets, you should setup a DNS for your subnet and route the Internet traffic to the "Corporate" gateway. When you setup DNS follow this rule: 4. If you have two or more DNS servers in different locations, each server should point itself as primary and each other as secondary. More details can be found here:

Troubleshooting DNS If you have two or more DNS servers in different locations, each server should point itself as primary and each other as secondary. ...
www.chicagotech.net/dnstroubleshooting.htm




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
"Daryl" <(E-Mail Removed)> wrote in message news:70365AFE-BFCB-468B-8217-(E-Mail Removed)...
We have a classroom environment as follows:

In a lab we will have 10 stand alone 2003 servers with AD installed and 10
Windows XP machines. We have an 11th stand alone "instructor" 2003 server.

All of the machines are connected to a university network through which they
have internet access, DHCP addresses, and other resources.

Method 1: If we use University settings for our DNS servers and default
Gateways, traffic gets routed through "corporate" firewalls and we have
difficulty with joining domains on our classroom servers, logins take
forever, accessing shares doesn't allways work, etc. We have been told this
is an issue with the organizations routing and that there is no easy fix
except to do use Method 2.

Method 2: If we "hard" code the default gateway and DNS server (on both the
2003 servers and XP workstations) to the IP address of "instructor" 2003
server everything seems to work better. Logins are fast, joining domains
works, etc. The only downside is that we can no longer access the Internet
to download drivers, patches and updates, etc.

Question 1: What is the best/easist way (using Method 2) to have the
"Instructor" 2003 server route traffic to the Internet (i.e. pass through any
traffic it does not recognize to the "corporate" default gateway) without
effecting any other computers on the university network?

Question 2: Any other ideas or suggestions as to how to make our lab
situation work?

Thanks for any help you can provide.



 
Reply With Quote
 
Daryl
Guest
Posts: n/a

 
      11-01-2006, 08:21 PM
Bob,

Thanks for the ideas. Unfortunatly there is only a single subnet, but I
will ask if it would be feasible to use a secondary one for our classroom
PC's.

There is no way to have the "corporate" DNS point to my DNS server as
secondary, but I can point mine towards theirs.

I have also tried to put a secondary IP address on all of the PC's
(Primary=my DNS server, secondary=corporate DNS), but this does not have the
desired effect.

The problem seems to be the default gateway. If I set it to the "corporate"
setting, the Internet works but local stuff becomes slow and unstable. If I
point it directly to my instructor server local stuff works great, but we
cannot route anything to the Internet.

I thought that if I routed everything to the instructor DNS server, then
gave it the corporate default gateway, it might forward on that route, but
this does not work.

My guess is that this cannot be done realistically without using a second
subnet, correct?

If I am able to get our group of servers and workstations on a seperate
subnet, what services or configurations must be done on the Instructor PC to
route traffic off of our subnet?

Thanks again.

"Robert L [MVP - Networking]" wrote:

> Assuming there are two subnets, you should setup a DNS for your subnet and route the Internet traffic to the "Corporate" gateway. When you setup DNS follow this rule: 4. If you have two or more DNS servers in different locations, each server should point itself as primary and each other as secondary. More details can be found here:
>
> Troubleshooting DNS If you have two or more DNS servers in different locations, each server should point itself as primary and each other as secondary. ...
> www.chicagotech.net/dnstroubleshooting.htm
>
>
>
>
> 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


 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      11-01-2006, 11:43 PM
For the routing to work, you need to point all of your machines at the
corporate gateway to get Internet access. But you don't need to use the
corporate DNS. Routing and DNS are quite independent.

You can point all of your "local" machines to your local DNS, so that
these machines work properly with AD. To resolve other URLs, set this DNS
server to forward to a public DNS or to the corpopate DNS server.

"Daryl" <(E-Mail Removed)> wrote in message
news:63DCBF63-11B1-4FEE-B489-(E-Mail Removed)...
> Bob,
>
> Thanks for the ideas. Unfortunatly there is only a single subnet, but I
> will ask if it would be feasible to use a secondary one for our classroom
> PC's.
>
> There is no way to have the "corporate" DNS point to my DNS server as
> secondary, but I can point mine towards theirs.
>
> I have also tried to put a secondary IP address on all of the PC's
> (Primary=my DNS server, secondary=corporate DNS), but this does not have
> the
> desired effect.
>
> The problem seems to be the default gateway. If I set it to the
> "corporate"
> setting, the Internet works but local stuff becomes slow and unstable. If
> I
> point it directly to my instructor server local stuff works great, but we
> cannot route anything to the Internet.
>
> I thought that if I routed everything to the instructor DNS server, then
> gave it the corporate default gateway, it might forward on that route, but
> this does not work.
>
> My guess is that this cannot be done realistically without using a second
> subnet, correct?
>
> If I am able to get our group of servers and workstations on a seperate
> subnet, what services or configurations must be done on the Instructor PC
> to
> route traffic off of our subnet?
>
> Thanks again.
>
> "Robert L [MVP - Networking]" wrote:
>
>> Assuming there are two subnets, you should setup a DNS for your subnet
>> and route the Internet traffic to the "Corporate" gateway. When you setup
>> DNS follow this rule: 4. If you have two or more DNS servers in different
>> locations, each server should point itself as primary and each other as
>> secondary. More details can be found here:
>>
>> Troubleshooting DNS If you have two or more DNS servers in different
>> locations, each server should point itself as primary and each other as
>> secondary. ...
>> www.chicagotech.net/dnstroubleshooting.htm
>>
>>
>>
>>
>> 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

>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
three nic routing with windows server 2003 jeff_pelech@portalberni.ca Windows Networking 5 09-30-2009 01:28 PM
Server 2003 RRAS Routing Myxx Windows Networking 3 08-05-2008 11:45 PM
Strange Routing with Server 2003 pashiib@hotmail.com Windows Networking 7 05-12-2006 02:38 PM
VPN Routing server 2003- Thanks in Advance for the help terry Windows Networking 1 08-06-2005 09:43 PM
IP Routing Across Dual-homed 2003 Server Todd Windows Networking 3 05-24-2005 04:47 PM



1 2 3 4 5 6 7 8 9 10 11