TIA,

Terry G Phillips

From other conversations we've had on this topic, it appears that there isn't a way to do this

If anyone has some new ideas in this area, they would be great to hear!

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

John

Server publishing listening on Port 80 of the external interface doesn't fix this problem. That's the default setting, and we've never seen the external client IP addresses on the internal web server.

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

But I am not using the WEB publishing portion of ISA server. I used server publishing and published port 80 (a Protocol definition I created for HTTP).

Try that. It works well for me.

Mike Murray

Since that time, I learned that indeed we were doing something wrong! You *can* use server publishing to publish an internal server on Port 80 of the external interface. It just takes a few tricks with the inbound web request listener.

There are some drawbacks. The major one is that you can publish only a single web site per IP address on the external interface of the ISA Server. Now, if you have a bunch of IP addresses, its not that much of a problem.

Another drawback is that you bypass the Web Proxy service, so you can to port and protocol redirection like you can with Web Publishing rules that use the Web Proxy service.

HTH,
Tom

quote:

---

Originally posted by Mike5558:
You guys are doing something wrong! I just looked at my IIS logs (server is published behind as server) and I have the real IP addresses of all the people hitting my wesbite.

But I am not using the WEB publishing portion of ISA server. I used server publishing and published port 80 (a Protocol definition I created for HTTP).

Try that. It works well for me.

Mike Murray

---

------------------
Tom Shinder
http://www.isaserver.org/shinder/

quote:

---

Originally posted by tshinder:
Hi Mike,

Since that time, I learned that indeed we were doing something wrong! You *can* use server publishing to publish an internal server on Port 80 of the external interface. It just takes a few tricks with the inbound web request listener.

There are some drawbacks. The major one is that you can publish only a single web site per IP address on the external interface of the ISA Server. Now, if you have a bunch of IP addresses, its not that much of a problem.

Another drawback is that you bypass the Web Proxy service, so you can to port and protocol redirection like you can with Web Publishing rules that use the Web Proxy service.

HTH,
Tom

---

quote:

---

Originally posted by tshinder:
Hi Mike,

Since that time, I learned that indeed we were doing something wrong! You *can* use server publishing to publish an internal server on Port 80 of the external interface. It just takes a few tricks with the inbound web request listener.

There are some drawbacks. The major one is that you can publish only a single web site per IP address on the external interface of the ISA Server. Now, if you have a bunch of IP addresses, its not that much of a problem.

Another drawback is that you bypass the Web Proxy service, so you can to port and protocol redirection like you can with Web Publishing rules that use the Web Proxy service.

HTH,
Tom

---

Mike

You are a genius!

Of course, Host Headers will allow you to publish multiple web sites on the default HTTP port 80 *on a single server*. That's a great idea and a fantastic tip!

However, I think I should have been more specific about my statements regarding publishing web sites using Server Publishing.

You can publish a single *server* per IP address on Port 80 of the external interface(s). Now, you can get around the single web site limitation by using Host Headers, and now that I think about it, you can even get around the single server (sort of) by redirecting requests to another server on the network by configuring forwarding on the IIS server itself.

You still lose out on reverse proxy functionality, and you can limit access to the ISA Server only by using client address sets. The Web Proxy service allows you to use user/group authentication to access the proxy server's interface, so you lose a level of security, if you need it.

Nevertheless, you guys have done some excellent work at getting around the problem.

Thanks!

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

\ Thanks

dont mind if im late with this posting ...

ive solved the Problem with getting original IP Address earlyer without ISA just W2k NAT & RRAS in activating in the TCP/IP Stack Settings the IP forwarding.

For MultiWebSite Hosting (IdolWild)

Create as many needed destination Sets like www.aaa.com Path /* (for hole domain otherwise just the path you need like OWA /exchange/*)

Create Publishing Rules for each destination . Thats it ..should work so did fine by me !

kind regards

Nuddelaug

What part is not working?

Tom

quote:

---

Originally posted by IdolWild:
Can someone explain the process of settings this up in a little more detail? I'm having a little trouble setting it up.

\ Thanks

---

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Get it Here!

- IdolWild

Thanks!