Re: Changing Corporate subnet address
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 10:21:43 -0400
Hugh Norsworthy <HughNorsworthy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Remote users connect from remote networks (hotel, airports, etc) that
often use the same subnet as my private subnet which causes
conflicting addressing (I don't know the technical terminology for
this).
You've got it. VPN users must not be using the same IP network as the
destination network uses.
I'm not using DHCP so all address are static assigned. DHCP
isn't my problem though,
Well, the *lack* of DHCP may be a problem, as it would be much easier to
change your client workstations on the 192.168.1.0 network if you didn't
have to visit desks. I suggest you implement DHCP now - since you probably
have to visit 50 desks anyway. DHCP is a godsend and I use it even on tiny
networks ...including DHCP reservations for printers. The only devices that
get static IPs are servers & routers/firewalls/APs.
it's DNS
No, this isn't a DNS issue.
and the effect changing subnet
addresses will have on AD.
It should be fine, but do this after hours/on a weekend. You may need to
have someone in the remote offices make firewall/router changes if you have
no (non-VPN) remote connectivity to them.
I have 2 DCs in the corporate site and at
least 1 DC in each remote site.
On each DC in the corporate side, you'll need to change its IP (and its
DNS/WINS addresses appropriately). If you do use WINS make sure the
push/pull partnership is updated with the correct IPs. You'll need to change
your firewall/VPN policy so that the remote networks know about the change.
You'll need to deal with your workstations and printers, which is going to
be the most time consuming bit.
Thanks for the reply.
"PeterD" wrote:
On Wed, 18 Jul 2007 09:02:09 -0700, Hugh Norsworthy
<HughNorsworthy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Many of our remote users connect to our corporate network from
Hotels, airports, and etc. through our ISA server running Routing
and Remote Access. The problem is our private network uses IP
subnet 192.168.1.XXX which is such a standard now that many hotels,
airline lounges, and hotspots are using the same. The remote users
connect and authenticate fine but cannot reach any corporate
resources such as Exchange server or internal websites.
The only solution I know is to change the local subnet addressing
but I don't know what the effect will be on DNS and Active
Directory. There are approximately 50 nodes on the corporate
network and I should also mention that in addition to the corporate
site I have 3 remote sites, all part of the same Domain and
connected via VPN using Cisco PIX. They are different subnets.
I would appreciate any advice or suggestions as to how to approach
this.
Q: How are your users connecting to the corporate network?
Thought: Though sometimes 'confusing' changing the subnet can be
relatively easy: create a new scope in the DHCP server, reassign any
static IPs to the new scope and have all users release/renew their IP
addresses. For a larger network, this process may not be practical,
and I'm sure others will have (better) solutions.
.
- Follow-Ups:
- Re: Changing Corporate subnet address
- From: Hugh Norsworthy
- Re: Changing Corporate subnet address
- References:
- Re: Changing Corporate subnet address
- From: PeterD
- Re: Changing Corporate subnet address
- Prev by Date: Re: Unable to resolve some websites...
- Next by Date: Re: Changing Corporate subnet address
- Previous by thread: Re: Changing Corporate subnet address
- Next by thread: Re: Changing Corporate subnet address
- Index(es):
Relevant Pages
|
