2004-09-16 17:21:16 UTC
have a vpn route to each other (hardware to hardware) everything went fine
until I migrated us to sbs2003 premium with ISA.
Now the folks in that 192.168.168.0/24 range cannot connect or ping to
everyone in our 192.168.1.0/24 range, so I cannot do a
server/connectcomputer to join them to the sbs domain.
I know I need to mostlikely create some kind of route or rule to tell ISA
that those folks are "local" but I can't seem to figure it out.
I added an entry in the LAT for them and restarted the micorsoft firewall
service (that IS the right one no?) (Do I have to restart the service after
making a change?)
I know I'm not too far off on this one
If I change my gateway on a workstation in the main office to be the old
setting, I can again ping the remote stations so I know the tunnel is still
active and running just fine. I was using remote desktop to those
workstations to test this stuff out.
I plan to put an 03 dc there shortly, my old w2k dc will be upgraded to 03
and made a dc in the sbs domain and placed there for authntication (good