Jump to content

Recommended Posts

Posted

Hey,

 

 

we have a cachepilot max and are thinking about moving it around in our current infrastructure.

 

we currently have lan>isa>cache>internet

 

but we would like it to be lan>cachepilot(node on the lan)>isa>internet

 

 

we know that the isa gateway will need to be the router. but are unsure of the settings needed changin on the cachepilot max.

 

we have a cachepilot max version 5.2.5 (rack mount style)

 

 

thanks for your help

Posted

Quick question... why :) - not being... obstructive.. but if we know why, then chances are you'll get better advice from myself and these other fine folk!

 

It may be worth noting that if you are doing authentication on the cachepilot this might break it.

Personally I would avoid (what looks like) a double NAT situation. These are no fun.

 

Also.. give us IPs. That might help.

Posted
Hi this is exactly how I have mine setup so it is only connected to the LAN and not directly to the WAN. All you should need to do is assign a valid internal IP address and set your ISA server as the gateway for the cachepilot. If you are using AD for authentication then I assume the cachepilot must already be joined to your domain. Depending on how you have your ISA server setup you may need to create a new rule to allow the cachepilot to send and recieve over the filter port (smartfilter is 4004 I think).
Guest Guest
Posted
Hey,

 

 

we have a cachepilot max and are thinking about moving it around in our current infrastructure.

 

we currently have lan>isa>cache>internet

 

but we would like it to be lan>cachepilot(node on the lan)>isa>internet

 

 

we know that the isa gateway will need to be the router. but are unsure of the settings needed changin on the cachepilot max.

 

we have a cachepilot max version 5.2.5 (rack mount style)

 

 

thanks for your help

 

To do it you have to go into the web gui.

 

Press shutdown

 

Unmount the cachepilot from the rack

 

Throw out of nearest window

 

:D

 

 

seriously though all you do is unplug the red interface and tell it to work in single NIC mode (in the web gui)

Posted

thanks for your help, thats been really useful, at least i now know its possible to do.

 

ive set it up as single nic mode with an IP within our LAN range (172.16.1.***), and changed the default route to the IP of our ISA. however i cant ping it or access the gui outside of the vlan its set within. eg. the cache is on 172.16.1.*** but it cant be accessed on another vlan of 172.16.2.***.

 

is there any settings i need to change on the cache?

Posted

Single nic mode is the way to go. Sorry - I misunderstood your original diagram.

If it can't see the other vlans, you'll need to give it a default gateway that allows it to communicate to the other vlans, or give the cachepilot an alias on each vlan if the unit itself supports this.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...