Re: IP Routing Issue
- From: "moncho" <moncho990009@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 07 Oct 2005 12:22:25 GMT
"Joe Williams" <Joe@xxxxxxxxxxxx> wrote in message
news:%23e6pTbPyFHA.2792@xxxxxxxxxxxxxxxxxxxxxxx
>I have a network with a current IP scheme of 175.8.28.x. The default
>gateway is 175.8.28.102
>
> I am trying to set up a new domain with an IP scheme of 192.168.1.x
>
> I have to leave the 175.8.28.x subnet up and running untilI am completely
> done with the domain setup
>
> The problem I am having is that if I setup the server with the 192.168.1.x
> IP and leave the default gateway as 175.8.28.102 I cannot get to the
> internet or ping any other 192.168.1.x clients or ping teh new domain
> (I.E. DNS does not seem to work properly with the gateway on a different
> subnet) We think the firewall might think we are IP spoofing when setting
> it up this way.
>
> How can I configure it so that the new subnet can comminucate with the old
> default gateway and thus get to the internet, resolve DNS, etc?
Others have answered your questions, but I have a little advice about the
internal
IP address you are going to use.
Use something other than 192.168.1.XXX address scheme. The reason I say
this
is because if you want VPN connections, many home based router equipment use
this addressing scheme and you may have some conflicts. Heck you have
thousands of other internal IP address that you could use that other
companies
or home users will never think of (example-10.234.25.XXX with a netmask
of 255.255.255.0). I only mention this from experience.
Others may disagree with my info but, in the words of Dennis Miller, "That
is just my
opinion, I could be wrong."
moncho
.
- References:
- IP Routing Issue
- From: Joe Williams
- IP Routing Issue
- Prev by Date: Re: Publish/Assign Office for 50 users
- Next by Date: Re: User type
- Previous by thread: Re: IP Routing Issue
- Next by thread: Gone in 1200 Seconds.
- Index(es):
Relevant Pages
|