Conflicts with HTTP.sys listener in W2k3 server.

[terraserve]

I use NAWS server w/W2k server,works flawlessly as 2Tb home multimedia server. I want to upgrade to W2K3 Server/64bit XP pro but HTTP.sys
listener service "knocks" NAWS server off of port 80. NAWS server says
"can not bind to port". I researched HTTP.sys at M$... concluded it was
"forceware" BS, tried to disable it by (1) deleting it, (2) trying to configure
it to listen to localhost or any other adapter besides the gigabit local LAN
which I use to serve the home site using M$ HTTPCFG utility, and (3)
trying to delay startup of NAWS by X seconds to bind after listener scans
adaptors. I finally gave up in frustration and ghosted back to W2Ksp4.
I would appreciate any suggestions to help me work around this problem
since I really would like to upgrade to W2k3. thank you for superior
software!

[Frozen]

Hi Terraserve,


I'm not sure if this will definitely solve your problem or not, but my first suggestion would be to remove IIS from your W2K3 instance. You can do so by going to "Control Panel -> Add / Remove Programs". Choose the "Add / Remove Windows Components" option on the left, and then completely uncheck IIS and any IIS related components. Note that this might require you to have your W2K3 install CD handy.


Let us know if that helps.


Regards,


Joe

[terraserve]

still have the problem. I use w2k3 eXPerience edition ,which already
is stripped of iiS 6. HTTp.sys is IMBEDDED in W2K3/XP pro SP2/and
Vista .

[Frozen]

Hi Terraserve,


Okay, I am aware of your problem now. I read up on the "http.sys" kernel mode driver that Microsoft provides in Win2K3 and up. Basically, they've changed the model for how they want server applications to talk to the network. Due to this change, the "http.sys" driver listens on port 80 all the time on all IP's by default, preventing a "normal" winsock based server from being able to open port 80 for listening.


Anyways, there is a Microsoft article that details how to re-configure "http.sys" to only listen on a specific IP, rather than all of your IP's, so that you can still use port 80 on one or more IP's. The article is targeted towards Windows Media Services, but I see no reason why the information doesn't still apply just the same in your situation:

http://support.microsoft.com/default.aspx?kbid=328728


As a side note -- from reading through the above article -- it appears that you may just be able to stop and disable the windows service named "http". I don't have a Win2k3 computer handy, but you may want to just try issuing this command and see if it frees up port 80 for you:

net stop http

If it does, I imagine you can just disable this service from starting with Windows, and you should be good.


Anyways, hope that helps.


Regards,

Joe

[terraserve]

I now am hooked on W2K3. Much faster than W2Ksp4 but I still have a slight compatibility problem with NAWS.
By the way thanks for the last post, it got me on the right track.
My problem is in the startup of NAWS,either by batch file or as a windows service. When the system first boots with or without HTTp.sys installed,
NAWS put out a message.."unable to bind to port..etc". I have tried to
leave http.sys installed and use httpcfg.exe to configure it to only listen
to (a)"phantom adaptor"10.254.254.254:80 (b) my real adaptor,but w/
different port i.e.10.127.127.25:8080 or (c) my other adaptor 24.152.xx.xx,etc. but no luck. When I do get the port binding message, I can hit the "START"button on NAWS and it operates normally, which is how I am running it now. In conclusion ,the best I can get either with
run as service or startup is a manually started webserver.
I understand this is not the NAWS developer issue but a M$ BS
tactic to get us locked into their bloated software regime,(by the way NAWS=2.4-5meg memory vs. IIS6=50-120meg!!)

To give more info on this problem let me elaborate on my startup scheme..

I run this batch:

Echo off
PING 127.0.0.254 -n 3 -w 1000 >NUL .... my delay...an experiment!!
Start /BelowNormal NetworkActivWebServerV3.5.exe

... my start..I've also tried normal priority,and just a strait shortcut start as well!

I run this in startup.

Also I've tried running as service,not minimizng on startup.etc.etc..
It seems even if you disable or configure HTTP.sys in any way it STILL
listens for the first few seconds after the adaptors initiate. M$ gives plenty
of info on the syntax for httpcfg/http but nothing on the boot behavior
of this kernel driver pain in the butt. They say you can run 2 or more devices over port 80 on http.sys but only if they can directly use the
driver to communicate.Since NAWS is not based on this driver it can not do this. Since this is a problem with XPsp2 and W2K3sp1, Im sure it will also be a issue with VISTA since they all have a similar architecture.

If anybody runs on any of the above OS'es I would appreciate any tips
you have . Thanks in advance.

[NetworkActiv]

Dear terraserve,

If adding a delay to the automatic starting of the server brings about success in its listening, then version 4.0 may bring about ease of its starting. In the preferences of version 4.0 is a field titled "Extra delay in milliseconds". If you enter a large delay (such as 5000) into this field, does the problem persist?

NetworkActiv Software

[terraserve]

No its not the delay in startup that allows NAWS to operate but the manual
delay of pressing the start button after NAWS already starts. I think the issue is windows will not release the adapters (and listens shortly-port 80-)until startup is finished.

the only thing I havent tried is to run NAWS from the registry...
HKLM\.....\microsoft\run.

If the delay option was in NAWS (after launch)that might allow
for proper operation because that is effectively what I am doing manually
pressing the "START" button after 1-2 seconds.

Is there any way I could try 4.0.. as a beta tester I would "hammer"
NAWS w/gigabit adaptors at 70-90 megs/sec w/2-3 gig downloads.
P.S. 3.5 does it very well except for this little startup/http.sys thing.
Thanks.

[NetworkActiv]

[terraserve]

THE DELAY WORKED..installed over 3.5 in NAWS directory. works perfect.
less than 1000 ms can't bind port 80 , but over 1500 ms..flawless
my port log shows windows(http.sys) listens for 1 sec after last adaptor
initiates then NAWS can bind after that. I set delay to 3000.

Be sure normal users configure HTTP.SYS in device manager.

download and install support tools for w2k3/xp , install,
open command prompt, type

httpcfg set iplisten -i xxx.xxx.xxx.xxx:80 (any IP but what your adapters IP is.)

confirm with:

httpcfg query iplisten

you will get return of:

IP ......... xxx.xxx.xxx.xxx:80

HTTP.sys will listen to this "ghost port" and not bother w/ the real ones.
even when I uninstalled the http driver or disabled it in device manager
it still listened for 1 second or more if I didnt httpcfg it. So
there it is. A combo of reconfiguring M$'s BS driver and your good
sense to add a onboard delay solved this problem...thank you very much...

[NetworkActiv]

It's good to hear that things are working acceptably now.