I'm getting frustrated with ISA server - only installed this the other week, and have terminal services successfully being published through it, but I'm struggling with Ranger Outpost!
I can tracert the address through to the interface of the ISA server, but traffic seems to get lost from there, and can't hit my outpost server. Have registered domain on both internal and external DNS, and ensured that the default gateway on the Outpost server is set to the ISA server. I'm guessing it's my settings on the ISA server, but being new to this beast (no training of course - I'll 'pick it up' - dear god!) I'm floundering a little.
Anyone got this scenario working who could give me a helping hand?
Why are you bothering with Ranger outpost when you have terminal services?
Terminal services is performing a different function, namely delivering SIMS to the classroom for e-registration and profiles within the boundries set by our LEA. I don't fancy licencing 1300 kids to use terminal services, so outpost is a much cheaper and more effective option in our scenario.
I can't believe no-one is running Outpost through an ISA server!
I'm trying to do the same thing, Ranger listening on 6543 but I can't setup ISA because it wants to know what protocol. I've even tried creating it's own protocol specifying the port number - still no joy and ISA doesn't even suggest a connection has been attempted :(
I'll post here if I find a solution...
I've managed to get the ISA server to connect to our Ranger Outpost server (testing that the ISA server rules permit the traffic to Ranger Outpost) - the required rules are:
Permit TCP port 6543 TO the Ranger Outpost server from Anywhere
Permit TCP port 6543 FROM the Ranger Outpost server from Anywhere
(the only reason I've used "anywhere" here is because I'm still testing and will eventually be using Ranger externally).
I had to create my own protocol for Ranger (TCP inbound 6543 and TCP outbound 6543) that my access rule uses.
At the moment I'm trying to get our ISP (KCN / KPSN) to make the relevant changes to the school's Cisco firewall. Once it's all up and running correctly I'll post back again.
In case anyone else tries this, I spent about 3 days looking into the problem on my own. Then 2 days with an EIS support desk supervisor, and then a further hour or so with Ranger. I then requested a refund...