Welcome to ISAserver.org

Web Publishing problem

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Web Publishing problem

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing problem - 7.Aug.2004 1:08:00 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

Hi there simple and unfortunately working with ISA 2000 perfectly.

Web publishing rule(ISA 2004):
General: eMule Web Server
Action: eMule Web Server
From: Anywhere
To: 192.168.0.xx
(forward the original header ...Checked)
(request appears to come from the original client)
Trafic: HTTP
Listener: HTTp listening on port 80 no HTTPS enabled listener.
Public name: www.public.com
Path: same as the internal /*
Bridging: Redirect request to port 700(eMule web server running on port 700 on the internal machine 192.168.0.xx)
Users: all users
Schedule: Always
Link translation: not entries

Problem is that the server is working everything is fine with opening the first page of the eMule web server but afrer any of the requests as follow:
http://www.public.com/?ses=1388767959&w=transfer
http://www.public.com/?ses=1388767959&w=server
etc....
Browser comes up with this message:
Technical Information (for support personnel)

Error Code: 500 Internal Server Error. The request is not supported. (50)
Funny everything is working under ISA 2000 perfectly or alone itself(server publishing ISA:700 -> Internal:700, I was thinking that URLScan for ISA is integrated in 2004 ISA version and this is an issue with it.
Http Filtering rule:
Methods: Allow all methods
Extensions: Allow all extentions
Header: Send the original header via header(default).

So if theis works under ISA 2000 where is the problem evrything else is working Citrix and it's .asp plus other .php pages working perfectly.
eMule Uses its own web server.
Where is the problem ?
with such requests
http://www.public.com/?ses=3843123207&w=server

Post #: 1

Featured Links*

RE: Web Publishing problem - 9.Aug.2004 6:07:00 AM

Uju Sivas

Posts: 236
Joined: 31.Dec.2001
Status: offline

has all your server's request is in same box and in same directroy as /*.... ?

Has the permission is being set correctly in first page and subsequent pages.... ?

(in reply to papata)

Post #: 2

RE: Web Publishing problem - 12.Aug.2004 12:33:00 AM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

yes it is and it's perfectly working with isa 2000 with a similar option destination set and then web publishing rule redirecting all requests to port 700 so nothing is changed since then just isa 2004 an the message from the top not supported request also there is nothing to do with permissions or so or the website itself as everything is working ok an any pages can be seen with ISA 200 with ISA 2004 - first logon page and index can be seen...afterwards Error Code: 500 Internal Server Error. The request is not supported. (50)Also whne talking about permision this is not IIS WEB Server eMule it's running its own web server have a look at emule site

[ August 12, 2004, 12:44 AM: Message edited by: papata ]

(in reply to papata)

Post #: 3

RE: Web Publishing problem - 17.Aug.2004 3:13:00 PM

chotie

Posts: 70
Joined: 27.Mar.2002
From: Sweden
Status: offline

Hello papata!

Did you ever got this to work?
I have also made the same tests as you and i also have this working perfectly in ISA2000.

Please give me a hint if you would find out something that would set it to work for you...

Thanks..

Br,
Christian O.

(in reply to papata)

Post #: 4

RE: Web Publishing problem - 21.Aug.2004 5:00:00 AM

eddieg

Posts: 26
Joined: 28.Aug.2002
Status: offline

Have you come up with anything? I know ISA 2004 worked fine for me until recently.

(in reply to papata)

Post #: 5

RE: Web Publishing problem - 21.Aug.2004 12:27:00 PM

chotie

Posts: 70
Joined: 27.Mar.2002
From: Sweden
Status: offline

I am thinking of going back to W2K and ISA2000.

I have had some advices from diffrent people but it turned out they did not try the config themself, actually... :/

Finally they said something about that some configurations were not supported by microsoft...

Nice way to get out of it.

Well - i will wait with upgrading for now..

Does anyone know if Thomas S. book takes up
web publishing on the same server as the ISA
is installed on?

Br,
Chotie

(in reply to papata)

Post #: 6

RE: Web Publishing problem - 22.Aug.2004 12:06:00 AM

tshinder

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online

Hi Chotie,

Yes, I'll include on-box publishing directions in the book.

HTH,
Tom

(in reply to papata)

Post #: 7

RE: Web Publishing problem - 16.Sep.2004 11:24:00 PM

lexvis

Posts: 1
Joined: 16.Sep.2004
Status: offline

papata, I've got the same problem and tried almost everything. Can't get it to work though... :-(

I can't find anything like it on Google, also. It's getting very frustrating, I hate it when things don't work like they're supposed to do.

More suggestions would be welcome!

(in reply to papata)

Post #: 8

RE: Web Publishing problem - 18.Sep.2004 12:00:00 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

I was wondering if theree is any config list for suported requests I ams sure is not that complicated.If anyone know how to configure the suported requests on isa2004 so all we know the answer I don't think that MS shoul put themselves in situation where people going back for ISA2000 on the end is their Firewall and this is where people expect ISA 2004 to be helpfull not pain in the butt

(in reply to papata)

Post #: 9

RE: Web Publishing problem - 27.Sep.2004 4:53:00 PM

penrose.l@2college.nl

Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline

Hi ,

To solve :

Make a entry in hosts file like this :
172.16.1.1 webmail.mydomain.com

where 172.16.1.1 is the INTERNAL ip of your webserver ( which you used to publish the webserver like webmail ).
When you ping webmail.mydomain.com your ISA will ping 172.16.1.1. Try it. If it doesn't work you made a mistake somewhere and need to start over until it works.

Now you can publish using the EXTERNAL name ( webmail.mydomain.com ) instead of 172.16.1.1
This has to do with host headers.
Be sure to send the original host header instead of the ISA one ( so DON'T tick it )

Kind regards,
Lex P

(in reply to papata)

Post #: 10

RE: Web Publishing problem - 14.Jun.2005 5:49:00 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

Error Code: 500 Internal Server Error. The request is not supported. (50)
Seems that the problem stll exist,even after host add and publishing that you recomended.
I still don't understand how things that works with isa 2000 are not suported under 2004 ?

[ June 14, 2005, 05:50 PM: Message edited by: papata ]

(in reply to papata)

Post #: 11

RE: Web Publishing problem - 10.Jun.2007 3:27:09 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

Works fine now after enabling ISA 2004 Web Compression Filter. It seems that earlier I haven't spotted that eMule custom web server uses GZIP compression. Well it does and just enabling the compression filter both to request compression from servers and to respond with compressed content solved the problem and eMule web interface works perfectly fine behind ISA 2004.

(in reply to papata)

Post #: 12

RE: Web Publishing problem - 14.Jun.2007 6:44:03 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

Forgot to mention that if anyone needs eD2K Links feture from the published Emule custom Webserver, the
ISA Web Publising Rule
->HTTP Security Filter Settings
->The General Tab
->Verify normalization
Should be cleared for the request to work.

(in reply to papata)

Post #: 13

RE: Web Publishing problem - 19.Mar.2008 7:50:40 PM

papata

Posts: 83
Joined: 1.Feb.2004
From: London
Status: offline

Here we go again, after all this time I still cannot publish properly eMule Web Control or uTorrent GUI.
Seems that the ISA Server 2004 sp3 on Windows 2003 SP2, no IIS web server installed on the ISA, web discovery on 8080 published in WPAD and working properly, Netstat -a -b showing no other apps taking over port 80, does not like port bridging so much in this case.

The problem lies with ISA Server port when publishing servers bridging to different ports than port 80.
Every time the web publishing bridging is set to different port 90 for example the following message appears in the LOG as an alert and I have to restart the service.
Well basically that is all...no extra publishing and no bridging to ports other than 80 and all the nice failure messages disappear.
The other cause of this could be the Sangoma 518 ADSL card, but i doubt it afer all the testing, the ISA is Front End Server.

Description: The Web Proxy filter failed to bind its socket to xxx.xxx.xxx.xxx port 80. The failure is due to error: 0x80072740

Any suggestions guys, I wont give up after all this time guys�
Couple of posts that relate to 0x80072740, it could be the ADSL Card and the DSLAM Hardware that is the cause, but still not convinced, since normal Web publisning never caused the message to appear, so the only thing that can be the reason is the Port Bridging in the Web Publisning Rule.
Also I don't want to create diferent Web Listener on separate ports, want to keep it to one web listener on standart port 80 and hopefully make redirection works.

http://forums.isaserver.org/fb.aspx?m=240105215

quote:

Another thing that can cause this is a power failure on the hub or switch the NIC is connected to. It only has to be a moment, so if the hub or swtich is not on a UPS, you'll see a lot of these.

http://forums.isaserver.org/fb.aspx?m=2002022474