Re: Tricky Site-to-Site VPN
- From: "Dan24" <dliberty@xxxxxxxxx>
- Date: 23 Jan 2007 06:55:46 -0800
Then I don't know why but the wizard is obvisouly missing something -
my system fails to boot after changing the IP (too many services are
hung, "Applying computer policy" takes more than an hour!!).
Still, changing the IP is something I'm trying to avoid since there are
external sources which also have this IP hardcoded (like other VPNs,
etc).
Jim Behning wrote:
That wizard is supposed to change the ip everywhere it is hard coded.
Sometimes the wizard acts up but almost always works. It should get
dhcp, dns, isa/rras, Exchange, wins, and IIS. A log is written to
%sbsprogramdir%/support. If you dig around in program files you should
see what that means.
Dan24 wrote:
That's currently not an option - I tried running and the wizard and
still after restart the server won't even come back up (stuck with
"Applying computer policy"). After more than an hour it finally shows
the log on screen with "One or more services could not start" and the
event log full of error messages. Even Exchange does not come back up.
I think the IP address is hardcoded in too many places.
Duncan McC wrote:
In article <1169509325.348152.15660@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
dliberty@xxxxxxxxx says...
Hi,I'd go with that - regardless - should come right if you re-run the wiz.
I am running an SBS 2003 with ISA 2004 server. I need to set up a
site-to-site tunnel to a 3rd party office.
Now basically, this is not really site-to-site because the only
communication needed here is for our SBS server to access an FTP on
their network securely (they insist it be done with an IPsec tunnel).
Usually I would have done this without a problem using ISA, but here's
where it gets complicated:
My SBS server's IP is 192.168.16.2. The 3rd party office which I'm
trying to create the tunnel with claim they cannot setup the tunnel
since they already have someone else tunneled in with with this IP
(192.168.16.2).
So at first I thought I'll try to set up an additional IP address on
our Internal NIC which is "available" to use on their side, but this
doesn't work since when trying to acess their server the source IP is
still 192.168.16.2.
I have also tried changing the IP address of my Internal NIC but this
caused about 50% of the services running on the server to hang/stop
functioning and so I consider this to be the worst case solution.
--
Duncan
.
- References:
- Tricky Site-to-Site VPN
- From: Dan24
- Re: Tricky Site-to-Site VPN
- From: Duncan McC
- Re: Tricky Site-to-Site VPN
- From: Dan24
- Re: Tricky Site-to-Site VPN
- From: Jim Behning
- Tricky Site-to-Site VPN
- Prev by Date: Re: Exchange no longer accepts inbound email
- Next by Date: Re: Pagefile on server with low space
- Previous by thread: Re: Tricky Site-to-Site VPN
- Next by thread: need hel with 2k3 sbs & isa in VPN config..
- Index(es):
Relevant Pages
|
