Re: 3 NIC IP routing issue & local dhp client issue
- From: "Bill Grant" <not.available@online>
- Date: Wed, 4 May 2005 10:20:19 +1000
Like Phillip I am not at all sure what you are trying to do here. But
here is a bit of advice. It is too complex. Running multiple NICs in a DC is
a bad idea. Using a DC as a router is a bad idea. Using a DC for remote
access is a bad idea. It can be done (else SBS wouldn't exist) but it can be
a real pain. You will find it all much simpler if you use a separate machine
for routing and remote access.
Why are you trying to run DHCP relay? Aren't all your DHCP clients on
the local LAN? Remember that the DHCP service must be authorised in AD
before it will work.
Grimmo' wrote:
> sorry, forgot some basic info:
>
> the dhcp relay agent is configured on both lan and wan interface (not
> the gateway nic). you are talking aboud broadcasting for the dhcp
> relay agent, do you mean that i should add a brodcast ip to the wan
> interface adapter? I have a reserved broadcast ip (81.0.176.167) that
> i could add, and a gw ip (81.0.176.166), both on subnet
> 255.255.255.248. I don't think that will make any difference to my
> problem, my main concern is to make the servers routing work for my
> dhcp clients.
>
> should I change the order of the adapter- an client bindings?
>
> the bindings for providers are:
>
> Windows Networks
> Terminal Services
> Web Client
>
> Adapter order is:
>
> LAN 192.168.16.2
> Wan 81.0.176.164
> Wan 195.1.30.229 (dgw 195.1.30.230)
> RAS Connections
>
> File/printer sharing and Client for MS Networks are only enabled on
> the lan adapter.
>
>
> hope this provides you with a little more help :-)
>
> ...::::--- no source, no pay ---::::...
>
>
> "Phillip Windell" wrote:
>
>> "Grimmo'" <Grimmo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:CEACB80E-3BE7-469E-BEF3-F79141D63794@xxxxxxxxxxxxxxxx
>>> Exchange has a dedicated interface on a separate NIC with the ip
>>> 81.0.176.164 on subnet 255.255.255.248, which is pingable from
>>> inside our domain, but not from the outside.
>>
>> Do you have a topology map that is accuarte? "Domains" are
>> irrelevant,...they have nothing to do with network
>> connectivity,...domains are a Windows Administration entity only.
>>
>> You are simply dealing with Layer3 routing among several subnets
>> that are all "directly connected" to the Server which is acting as
>> its own router,...can you re-describe the problem with that in mind?
>>
>>> In addition to this, my dhcp clients won't recieve dhcp.
>>
>> DHCP will not work across subnets,...it is broadcast based. For it
>> to work accross subnets with RRAS you must add/configure the DHCP
>> Agent in RRAS.
>>
>>> I found a temp solution earlier by disabling RRAS and enabling ICS,
>>> but after altering my routing table and bindings order for my NIC's
>>> (LAN on top), it won't work at all.
>>
>> That was not a temporary solution, you only created a situation that
>> created a "deception" that made things appear to be working in a
>> certain way when they were not. There is no way that ICS should
>> ever be used in this situation, at all, ever.
>>
>> --
>>
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
.
- Follow-Ups:
- Re: 3 NIC IP routing issue & local dhp client issue
- From: Grimmo'
- Re: 3 NIC IP routing issue & local dhp client issue
- References:
- 3 NIC IP routing issue & local dhp client issue
- From: Grimmo'
- Re: 3 NIC IP routing issue & local dhp client issue
- From: Grimmo'
- 3 NIC IP routing issue & local dhp client issue
- Prev by Date: Re: UNC, VPN site to site
- Next by Date: Re: Reverse DNS
- Previous by thread: Re: 3 NIC IP routing issue & local dhp client issue
- Next by thread: Re: 3 NIC IP routing issue & local dhp client issue
- Index(es):
Relevant Pages
|
