Discussion:
SecureClient / VPN Domain question
(too old to reply)
p***@yahoo.com
2007-02-07 21:27:35 UTC
Permalink
My company was recently bought by another company so I had to switch
IP schemes. The scheme they are using is 10.0.0.0/255.0.0.0 and that
is what I have defined as my VPN domain on my firewall. Now when
SecureClients are on a 10. network they can not authenticate or access
network resources.

I was thinking of making the VPN domain a smaller network range but
that would stop the SecureClients from communicating with other parts
of the network. My network segment is actually 10.170.4.0/22 but
SecureClients would need to communicate with several other 10.
networks (10.160, 10.150, ect..)

Can anyone give me an idea on how this might be setup?

Thanks,
Dan
Mr.U
2007-02-08 09:51:33 UTC
Permalink
Use a feature called "Office Mode"
JJ
2007-02-09 03:16:26 UTC
Permalink
Office Mode and dynamic interface resolving will do the trick. If there's
not that many 10. networks, you should just define the ones you use anyway.

Ray
Post by p***@yahoo.com
My company was recently bought by another company so I had to switch
IP schemes. The scheme they are using is 10.0.0.0/255.0.0.0 and that
is what I have defined as my VPN domain on my firewall. Now when
SecureClients are on a 10. network they can not authenticate or access
network resources.
I was thinking of making the VPN domain a smaller network range but
that would stop the SecureClients from communicating with other parts
of the network. My network segment is actually 10.170.4.0/22 but
SecureClients would need to communicate with several other 10.
networks (10.160, 10.150, ect..)
Can anyone give me an idea on how this might be setup?
Thanks,
Dan
p***@yahoo.com
2007-02-12 21:53:43 UTC
Permalink
Post by JJ
Office Mode and dynamic interface resolving will do the trick. If there's
not that many 10. networks, you should just define the ones you use anyway.
Ray
Post by p***@yahoo.com
My company was recently bought by another company so I had to switch
IP schemes. The scheme they are using is 10.0.0.0/255.0.0.0 and that
is what I have defined as my VPN domain on my firewall. Now when
SecureClients are on a 10. network they can not authenticate or access
network resources.
I was thinking of making the VPN domain a smaller network range but
that would stop the SecureClients from communicating with other parts
of the network. My network segment is actually 10.170.4.0/22 but
SecureClients would need to communicate with several other 10.
networks (10.160, 10.150, ect..)
Can anyone give me an idea on how this might be setup?
Thanks,
Dan- Hide quoted text -
- Show quoted text -
I am using Office Mode which is set to a 192.168.123.0/255.255.255.0
network. I did some testing in my test environment and from my home
network and found that any time I set my client IP range to 10.
anything it doesn't work. It won't even authenticate let alone get a
Office Mode address.

Dan
Mr.U
2007-02-13 10:11:04 UTC
Permalink
Have you used: dynamic interface resolving as JJ told you?

Loading...