|
Did you do route add with the persistent switch?
John Tolmachoff Engineer/Consultant/Owner eServices For You
-----Original Message-----
Thanks, I think. Actually, I did register and post there, using a different email address. I posted under the Server Publishing forum this morning, as “Johnny Quest”.
Nevertheless, I figured it out. I was doing it right from the beginning…BUT: for reasons I don’t quite understand my NT server DOES NOT keep the default gateway even when assigned manually in the TCPIP Properties. This was of course killing me.
I manually added the route 0.0.0.0 through the default gateway and immediately it all started working. Even my web publishing rule that redirects to the 8383 so users don’t have to manually input the port number. The server looses the route after rebooting, so I’ll have to manually set it each time I restart the box. Not sure why, but I’m not too concerned about that part of it.
-- V�ctor
-----Original Message-----
But you did not join the e-mail list on isaserver.org and posted their. If you had done so, I would have answered.
John Tolmachoff Engineer/Consultant/Owner eServices For You
-----Original Message-----
Hello All, I hope I don’t get flamed for this post…I’ve spent HOURS on isaserver.org online trying to find an answer, to no avail, so I turn to your expertise.
I’ve just installed Imail Xpress on an NT server that is a SecureNAT client (no firewall client installed) of my dual-homed ISA Server.
I created custom protocol rules for the Imail ports – 8383, 8484, 106, etc.
I created a destination set pointing to my imail server.
I then created server publishing rules for each of the Imail custom protocols and pointed them at the new destination set, then ran the Secure Mail Server Wizard to publish the smtp, pop3 and imap services running on the NT/Imail box.
No go. The only way I’m able to get to the web messaging login page is by creating a web publishing rule that redirects http calls to port 8383. W/that, I get the login page and I’m able to log into Imail, compose messages, and do anything that doesn’t require any other port. As soon as I select Web Calendaring, it blows up, since it’s trying to connect to port 8484 for that.
I’ve disabled socket pooling on the ISA server just to eliminate that as a possible problem, even though I’m not running any of the Imail services on it. I have not created packet filters, since you’re not supposed to need these for server publishing. I have not created any protocol rules for the NT server.
I’ve also posted this under the server publishing forum of isaserver.org in the hopes of getting some expert advice there as well….
Thanks in advance!
V�ctor |
- [IMail Forum] Imail behind ISA Server question Amram, Victor
- RE: [IMail Forum] Imail behind ISA Server q... John Tolmachoff \(Lists\)
- RE: [IMail Forum] Imail behind ISA Server q... John Tolmachoff \(Lists\)
- RE: [IMail Forum] Imail behind ISA Server q... Amram, Victor
- RE: [IMail Forum] Imail behind ISA Serv... John Tolmachoff \(Lists\)
- RE: [IMail Forum] Imail behind ISA Serv... John Tolmachoff \(Lists\)
- RE: [IMail Forum] Imail behind ISA Server q... Amram, Victor
- RE: [IMail Forum] Imail behind ISA Serv... John Tolmachoff \(Lists\)
- RE: [IMail Forum] Imail behind ISA Server q... Amram, Victor
