|
Home > Archive > alt.certification.mcse > May 2003 > Routing through Dual Homed 2k Server?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Routing through Dual Homed 2k Server?
|
|
| Dr Zoidberg 2003-05-15, 8:24 am |
| At present I have a cable modem going into an SMC router which is
sharing the connection 4 ways.
All four machines that are connected directly are behaving as they should.
My network is split into two halves , a workgroup and domain.
The three machines that are part of a workgroup are taking up three of the
ports on the router.
The fourth port goes to a machine running windows 2000 server as a domain
controller which has 2 NICs fitted.
The interface connected to the router has a static IP address (192.168.2.41)
and is set to use the router (192.168.2.1) as its default gateway. This is
fine and the server has net connectivity.
The second interface on the server has a static IP address (192.168.1.41)
and is correctly allocating IP addresses via DHCP to client machines
attached (scope 192.168.1.1-40)
These client machines can log onto the servers domain , browse shared
folders and so on. What they can not do is connect to the net.
It's not a DNS issue , as if I ping a website form a client machine it gets
correctly resolved to an IP address but all packets time out.
The routing table on the client machines seems ok as the default gateway is
correctly set to 192.168.1.41 and I can ping the server (both IP addresses)
If I try and ping my router from the client (through the server) I get
timeouts , so it seems that the server isn't forwarding packets.
RRAS is enabled on the server , and IP routing is activated.
The routing table from the server is as follows.
Any suggestions where things are going wrong?
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>route print
==============================
==============================
===============
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 00 62 a1 79 65 ...... Intel DC21041 PCI Ethernet Adapter
0x1000004 ...00 20 78 1b 13 23 ...... Winbond W89C940 PCI Network Adapter.
==============================
==============================
===============
==============================
==============================
===============
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.1.41 1
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.41 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
192.168.1.41 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.41 192.168.1.41 1
192.168.2.0 255.255.255.0 192.168.2.41 192.168.2.41 1
192.168.2.41 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.41 192.168.2.41 1
224.0.0.0 224.0.0.0 192.168.1.41 192.168.1.41 1
224.0.0.0 224.0.0.0 192.168.2.41 192.168.2.41 1
255.255.255.255 255.255.255.255 192.168.2.41 192.168.2.41 1
Default Gateway: 192.168.2.1
==============================
==============================
===============
Persistent Routes: None
--
Alex
"We are now up against live, hostile targets"
"So, if Little Red Riding Hood should show up with a bazooka and a bad
attitude, I expect you to chin the XXXXX! "
www.drzoidberg.co.uk
| |
| Andy Barkl 2003-05-15, 9:26 am |
| "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
news:1053002143.36094.0@damia.uk.clara.net...
> The routing table on the client machines seems ok as the default gateway
is
> correctly set to 192.168.1.41 and I can ping the server (both IP
addresses)
>
> If I try and ping my router from the client (through the server) I get
> timeouts , so it seems that the server isn't forwarding packets.
>
> RRAS is enabled on the server , and IP routing is activated.
>
> The routing table from the server is as follows.
>
> Any suggestions where things are going wrong?
> Alex
>
> "We are now up against live, hostile targets"
>
> "So, if Little Red Riding Hood should show up with a bazooka and a bad
> attitude, I expect you to chin the XXXXX! "
>
> www.drzoidberg.co.uk
You need to add the 192.168.1.0 network route to the router for the return
path.
| |
| Dr Zoidberg 2003-05-15, 10:25 am |
| Andy Barkl wrote:
> "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
> news:1053002143.36094.0@damia.uk.clara.net...
>> The routing table on the client machines seems ok as the default
>> gateway is correctly set to 192.168.1.41 and I can ping the server
>> (both IP addresses)
>>
>> If I try and ping my router from the client (through the server) I
>> get timeouts , so it seems that the server isn't forwarding packets.
>>
>> RRAS is enabled on the server , and IP routing is activated.
>>
>> The routing table from the server is as follows.
>>
>> Any suggestions where things are going wrong?
>
> You need to add the 192.168.1.0 network route to the router for the
> return path.
I have this in the routing table already
Network
Destination Netmask Gateway Interface
Metric
192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
which should be the return path
--
Alex
"We are now up against live, hostile targets"
"So, if Little Red Riding Hood should show up with a bazooka and a bad
attitude, I expect you to chin the XXXXX! "
www.drzoidberg.co.uk
| |
| wcrouse 2003-05-15, 1:25 pm |
| Have you configured network address translation (NAT) to run as part
of your RRAS setup? If not, packets won't make it across your server
and your domain machines will be quite isolated and secure from the
web (sometimes a good thing). Also, even though a server is multihomed
it may still have only one gateway configured. Got caught on this one
myself not long ago.
On Thu, 15 May 2003 13:35:42 +0100, "Dr Zoidberg"
<AlexcookNOOOOOO!!!!!@Cwcom.net> wrote:
>At present I have a cable modem going into an SMC router which is
>sharing the connection 4 ways.
>All four machines that are connected directly are behaving as they should.
>
>My network is split into two halves , a workgroup and domain.
>The three machines that are part of a workgroup are taking up three of the
>ports on the router.
>
>The fourth port goes to a machine running windows 2000 server as a domain
>controller which has 2 NICs fitted.
>The interface connected to the router has a static IP address (192.168.2.41)
>and is set to use the router (192.168.2.1) as its default gateway. This is
>fine and the server has net connectivity.
>
>The second interface on the server has a static IP address (192.168.1.41)
>and is correctly allocating IP addresses via DHCP to client machines
>attached (scope 192.168.1.1-40)
>These client machines can log onto the servers domain , browse shared
>folders and so on. What they can not do is connect to the net.
>It's not a DNS issue , as if I ping a website form a client machine it gets
>correctly resolved to an IP address but all packets time out.
>
>The routing table on the client machines seems ok as the default gateway is
>correctly set to 192.168.1.41 and I can ping the server (both IP addresses)
>
>If I try and ping my router from the client (through the server) I get
>timeouts , so it seems that the server isn't forwarding packets.
>
>RRAS is enabled on the server , and IP routing is activated.
>
>The routing table from the server is as follows.
>
>Any suggestions where things are going wrong?
>
>
>Microsoft Windows 2000 [Version 5.00.2195]
>(C) Copyright 1985-2000 Microsoft Corp.
>
>C:\>route print
> ==============================
==============================
===============
>Interface List
>0x1 ........................... MS TCP Loopback interface
>0x1000003 ...00 00 62 a1 79 65 ...... Intel DC21041 PCI Ethernet Adapter
>0x1000004 ...00 20 78 1b 13 23 ...... Winbond W89C940 PCI Network Adapter.
> ==============================
==============================
===============
> ==============================
==============================
===============
>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.2.1 192.168.1.41 1
> 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.41 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
> 192.168.1.41 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.41 192.168.1.41 1
> 192.168.2.0 255.255.255.0 192.168.2.41 192.168.2.41 1
> 192.168.2.41 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.2.255 255.255.255.255 192.168.2.41 192.168.2.41 1
> 224.0.0.0 224.0.0.0 192.168.1.41 192.168.1.41 1
> 224.0.0.0 224.0.0.0 192.168.2.41 192.168.2.41 1
> 255.255.255.255 255.255.255.255 192.168.2.41 192.168.2.41 1
>Default Gateway: 192.168.2.1
> ==============================
==============================
===============
>Persistent Routes: None
| |
| Dr Zoidberg 2003-05-15, 1:25 pm |
| wcrouse wrote:
> Have you configured network address translation (NAT) to run as part
> of your RRAS setup? If not, packets won't make it across your server
> and your domain machines will be quite isolated and secure from the
> web (sometimes a good thing). Also, even though a server is multihomed
> it may still have only one gateway configured. Got caught on this one
> myself not long ago.
>
The router is doing all the NAT from private to public addressing , so its
not needed on the server. The problem is that the server is refusing to pass
packets between the two subnets on the two NICs. Very frustrating.
--
Alex
"We are now up against live, hostile targets"
"So, if Little Red Riding Hood should show up with a bazooka and a bad
attitude, I expect you to chin the XXXXX! "
www.drzoidberg.co.uk
| |
| Andy Barkl 2003-05-15, 3:24 pm |
| "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
news:1053009016.51832.0@iapetus.uk.clara.net...
> Andy Barkl wrote:
> > "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
> > news:1053002143.36094.0@damia.uk.clara.net...
> >> The routing table on the client machines seems ok as the default
> >> gateway is correctly set to 192.168.1.41 and I can ping the server
> >> (both IP addresses)
> >>
> >> If I try and ping my router from the client (through the server) I
> >> get timeouts , so it seems that the server isn't forwarding packets.
> >>
> >> RRAS is enabled on the server , and IP routing is activated.
> >>
> >> The routing table from the server is as follows.
> >>
> >> Any suggestions where things are going wrong?
> >
> > You need to add the 192.168.1.0 network route to the router for the
> > return path.
>
> I have this in the routing table already
> Network
> Destination Netmask Gateway Interface
> Metric
> 192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
>
> which should be the return path
> --
> Alex
>
> "We are now up against live, hostile targets"
>
> "So, if Little Red Riding Hood should show up with a bazooka and a bad
> attitude, I expect you to chin the XXXXX! "
>
> www.drzoidberg.co.uk
You need to add the route to your "other" router.
| |
| Dr Zoidberg 2003-05-15, 3:24 pm |
| Andy Barkl wrote:
> "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
> news:1053009016.51832.0@iapetus.uk.clara.net...
>> Andy Barkl wrote:
>>> "Dr Zoidberg" <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote in message
>>> news:1053002143.36094.0@damia.uk.clara.net...
>>>> The routing table on the client machines seems ok as the default
>>>> gateway is correctly set to 192.168.1.41 and I can ping the server
>>>> (both IP addresses)
>>>>
>>>> If I try and ping my router from the client (through the server) I
>>>> get timeouts , so it seems that the server isn't forwarding
>>>> packets.
>>>>
>>>> RRAS is enabled on the server , and IP routing is activated.
>>>>
>>>> The routing table from the server is as follows.
>>>>
>>>> Any suggestions where things are going wrong?
>>>
>>> You need to add the 192.168.1.0 network route to the router for the
>>> return path.
>>
>> I have this in the routing table already
>> Network
>> Destination Netmask Gateway Interface
>> Metric
>> 192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
>>
>> which should be the return path
>> --
>> Alex
>>
>> "We are now up against live, hostile targets"
>>
>> "So, if Little Red Riding Hood should show up with a bazooka and a
>> bad attitude, I expect you to chin the XXXXX! "
>>
>> www.drzoidberg.co.uk
>
> You need to add the route to your "other" router.
Ta
--
Alex
"We are now up against live, hostile targets"
"So, if Little Red Riding Hood should show up with a bazooka and a bad
attitude, I expect you to chin the XXXXX! "
www.drzoidberg.co.uk
| |
| someone 2003-05-16, 2:25 pm |
| You need to remove the first route.
Internet access for you 2nd dhcsp lan must go thru the server gateway
address.
On Thu, 15 May 2003 13:35:42 +0100, "Dr Zoidberg"
<AlexcookNOOOOOO!!!!!@Cwcom.net> wrote:
>At present I have a cable modem going into an SMC router which is
>sharing the connection 4 ways.
>All four machines that are connected directly are behaving as they should.
>
>My network is split into two halves , a workgroup and domain.
>The three machines that are part of a workgroup are taking up three of the
>ports on the router.
>
>The fourth port goes to a machine running windows 2000 server as a domain
>controller which has 2 NICs fitted.
>The interface connected to the router has a static IP address (192.168.2.41)
>and is set to use the router (192.168.2.1) as its default gateway. This is
>fine and the server has net connectivity.
>
>The second interface on the server has a static IP address (192.168.1.41)
>and is correctly allocating IP addresses via DHCP to client machines
>attached (scope 192.168.1.1-40)
>These client machines can log onto the servers domain , browse shared
>folders and so on. What they can not do is connect to the net.
>It's not a DNS issue , as if I ping a website form a client machine it gets
>correctly resolved to an IP address but all packets time out.
>
>The routing table on the client machines seems ok as the default gateway is
>correctly set to 192.168.1.41 and I can ping the server (both IP addresses)
>
>If I try and ping my router from the client (through the server) I get
>timeouts , so it seems that the server isn't forwarding packets.
>
>RRAS is enabled on the server , and IP routing is activated.
>
>The routing table from the server is as follows.
>
>Any suggestions where things are going wrong?
>
>
>Microsoft Windows 2000 [Version 5.00.2195]
>(C) Copyright 1985-2000 Microsoft Corp.
>
>C:\>route print
> ==============================
==============================
===============
>Interface List
>0x1 ........................... MS TCP Loopback interface
>0x1000003 ...00 00 62 a1 79 65 ...... Intel DC21041 PCI Ethernet Adapter
>0x1000004 ...00 20 78 1b 13 23 ...... Winbond W89C940 PCI Network Adapter.
> ==============================
==============================
===============
> ==============================
==============================
===============
>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.2.1 192.168.1.41 1
> 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.41 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41 1
> 192.168.1.41 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.41 192.168.1.41 1
> 192.168.2.0 255.255.255.0 192.168.2.41 192.168.2.41 1
> 192.168.2.41 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.2.255 255.255.255.255 192.168.2.41 192.168.2.41 1
> 224.0.0.0 224.0.0.0 192.168.1.41 192.168.1.41 1
> 224.0.0.0 224.0.0.0 192.168.2.41 192.168.2.41 1
> 255.255.255.255 255.255.255.255 192.168.2.41 192.168.2.41 1
>Default Gateway: 192.168.2.1
> ==============================
==============================
===============
>Persistent Routes: None
| |
|
| so wat is the final solution?! did it work Alex?!
"someone" <someone@aol.com> wrote in message
news:a3eacv0puu9nqtn5ph9clmeqn
evsd10h1c@4ax.com...
> You need to remove the first route.
> Internet access for you 2nd dhcsp lan must go thru the server gateway
> address.
>
>
>
> On Thu, 15 May 2003 13:35:42 +0100, "Dr Zoidberg"
> <AlexcookNOOOOOO!!!!!@Cwcom.net> wrote:
>
> >At present I have a cable modem going into an SMC router which is
> >sharing the connection 4 ways.
> >All four machines that are connected directly are behaving as they
should.
> >
> >My network is split into two halves , a workgroup and domain.
> >The three machines that are part of a workgroup are taking up three of
the
> >ports on the router.
> >
> >The fourth port goes to a machine running windows 2000 server as a domain
> >controller which has 2 NICs fitted.
> >The interface connected to the router has a static IP address
(192.168.2.41)
> >and is set to use the router (192.168.2.1) as its default gateway. This
is
> >fine and the server has net connectivity.
> >
> >The second interface on the server has a static IP address (192.168.1.41)
> >and is correctly allocating IP addresses via DHCP to client machines
> >attached (scope 192.168.1.1-40)
> >These client machines can log onto the servers domain , browse shared
> >folders and so on. What they can not do is connect to the net.
> >It's not a DNS issue , as if I ping a website form a client machine it
gets
> >correctly resolved to an IP address but all packets time out.
> >
> >The routing table on the client machines seems ok as the default gateway
is
> >correctly set to 192.168.1.41 and I can ping the server (both IP
addresses)
> >
> >If I try and ping my router from the client (through the server) I get
> >timeouts , so it seems that the server isn't forwarding packets.
> >
> >RRAS is enabled on the server , and IP routing is activated.
> >
> >The routing table from the server is as follows.
> >
> >Any suggestions where things are going wrong?
> >
> >
> >Microsoft Windows 2000 [Version 5.00.2195]
> >(C) Copyright 1985-2000 Microsoft Corp.
> >
> >C:\>route print
>
> ==============================
==============================
===============
> >Interface List
> >0x1 ........................... MS TCP Loopback interface
> >0x1000003 ...00 00 62 a1 79 65 ...... Intel DC21041 PCI Ethernet Adapter
> >0x1000004 ...00 20 78 1b 13 23 ...... Winbond W89C940 PCI Network
Adapter.
>
> ==============================
==============================
===============
>
> ==============================
==============================
===============
> >Active Routes:
> >Network Destination Netmask Gateway Interface
Metric
> > 0.0.0.0 0.0.0.0 192.168.2.1 192.168.1.41
1
> > 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.41
1
> > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
> > 192.168.1.0 255.255.255.0 192.168.1.41 192.168.1.41
1
> > 192.168.1.41 255.255.255.255 127.0.0.1 127.0.0.1
1
> > 192.168.1.255 255.255.255.255 192.168.1.41 192.168.1.41
1
> > 192.168.2.0 255.255.255.0 192.168.2.41 192.168.2.41
1
> > 192.168.2.41 255.255.255.255 127.0.0.1 127.0.0.1
1
> > 192.168.2.255 255.255.255.255 192.168.2.41 192.168.2.41
1
> > 224.0.0.0 224.0.0.0 192.168.1.41 192.168.1.41
1
> > 224.0.0.0 224.0.0.0 192.168.2.41 192.168.2.41
1
> > 255.255.255.255 255.255.255.255 192.168.2.41 192.168.2.41
1
> >Default Gateway: 192.168.2.1
>
> ==============================
==============================
===============
> >Persistent Routes: None
>
|
|
|
|
|