Re: Need Help with RRAS
- From: "\"1SE\"" <smlbusnet.NOSPAM@xxxxxxxxxxx>
- Date: Fri, 15 Apr 2005 09:12:26 -0400
This is IN FACT true that it is NATing and I cannot see the 192.168.8.x
network.
I have set the primary DNS servers to the 192.168.8.x DC but since it cannot
be seen this does no good.
"Bill Grant" <not.available@online> wrote in message
news:%23ilFnW7PFHA.2788@xxxxxxxxxxxxxxxxxxxxxxx
> Good point, Phillip. It wouldn't be the first time we have seen
problems
> connecting to a remote access server in a DMZ which couldn't see the
private
> LAN, would it?
>
> Phillip Windell wrote:
> > "Bill Grant" <not.available@online> wrote in message
> > news:%23DP8qMWPFHA.3188@xxxxxxxxxxxxxxxxxxxxxxx
> >> I would manually configure the remote client to use your local
> >> DNS (ie the one for your 192.168.8 network) in the connection
> >> properties. To be able to resolve names by just using the machine
> >> name, also set the domain suffix to the suffix of this network.
> >
> > Bill,
> > If the Windows Server is running NAT then the 192.168.8 network won't
> > be at all reachable. The 172.16.7 network is effectively a DMZ in a
> > Back-toBack DMZ model, which is "untrusted" by the 192.168.8 network.
> >
> > If the Windows Server is not running NAT (just routing only) then it
> > probably should only run one Nic since the 172.16.7 network is just a
> > "useless appendage" sort of speak.
> >
> > I think he needs to clarify that when he gets back to make it more
> > clear what is being dealt with.
>
>
.
- References:
- Need Help with RRAS
- From: \"1SE\"
- Re: Need Help with RRAS
- From: Bill Grant
- Re: Need Help with RRAS
- From: \"1SE\"
- Re: Need Help with RRAS
- From: Bill Grant
- Re: Need Help with RRAS
- From: Bill Grant
- Need Help with RRAS
- Prev by Date: Split Tunnelling
- Next by Date: RE: 2003 Std Server: ICS disapered and stopped working after SP1
- Previous by thread: Re: Need Help with RRAS
- Next by thread: Print Error - Unable to connect
- Index(es):
Relevant Pages
|
