Re: 3 NIC IP routing issue & local dhp client issue

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

hello, bill!!

apprreciate your advice, and concurr with your and Philip's toughts. I'd
really like to understand, and implement your configl if I only knew that
you understand the issues taht I am targeting.... that really shouldn't be
that complicated. But, afterall, it obvioously seems it is...

I see that it isn't such a good idea to use my pdc as an rras/vpn/gateway
server, but for my company it is indeed a cost issue. I have a HP pl 140 that
is supposed to act as our webserver outside our local domain (NO other
roles), and a custom built sql server running MBS Navision (NOT to be visible
to the internet).

I need to have a server that routes our dhcp clients to the internet, also
being able to connect to their exchange mailboxes (assuring that they can
send/ recieve email), resolving DNS names and lookup wins names.

due to the routing table, and the netdiag/dcdiag tables provided for you
(top of this post), the tasks should be obvious, but the resolution might be
much less obvious.

I have been workingg really late night shifts trying to solve this problem,
but haven't gotten there yet...




....::::--- no source, no pay ---::::...


"Bill Grant" wrote:

> 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
>
>
>
.

Relevant Pages

  • Re: 3 NIC IP routing issue & local dhp client issue
    ... Why are you trying to run DHCP relay? ... Aren't all your DHCP clients on ... the local LAN? ... > i could add, and a gw ip, both on subnet ...
    (microsoft.public.windows.server.networking)
  • Re: dhcp
    ... and setting up the Lan with dhcp. ... then I suggest flushing its routing tables w/ ... >>network topology anew (sometimes network changes are not ...
    (comp.sys.ibm.pc.hardware.networking)
  • Re: Problems with Internet / Netgear router on SBS 2003
    ... Your SBS network has a 'lan' side; your SBS should be the DHCP server for ... The router also has a 'lan' side, and it's on the same addressing as your ... You can elect to turn on the DHPC server for your router; ... Even without DHCP turned on at the router, you can still connect there, you ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... have the LAN side of the wireless router be in the 10.0.0.x ... your SBS has two nics - its WAN nic is using 10.0.0.2 ... The SBS handles DHCP for the ... The SBS firewall not only keeps the wireless clients ...
    (microsoft.public.windows.server.sbs)
  • Re: LM98/2 Session refused
    ... there is no LAN connection at all. ... It's not a LM98 problem as such, it's a Win 7 machine problem that holds ... The Hosts file on this RPC contains an entry for the Win 7 machine of both ... With regard to DHCP everything on this network has a fixed address, ...
    (comp.sys.acorn.networking)