WWW Publishing Service 1

[2know]

What makes the NT 4.0 World Wide Publishing Service stop on it's own? I have this happening 1-2 times a week on a Proxy server and an Exchange server. Nothing is reported in the event log indicating it stopped.

 

[FilthPig]

The last place I worked, running Microsoft Proxy 2.0 in what sounds like a similar setup, we ended up authenticating people to our firewall and uninstalling proxy. After we did that,

http://WWW publishing

worked like a champ. MS Proxy is, in my opinion, not worth the trouble. Marc Creviere

 

[blinkinpark83]

Hi,

i've got a similar setup and the

http://www publishing

service does the same thing. not using ms proxy 2.0 is'nt really a fix. Has anyone got any ideas on this?

Thanks in advance

John.

 

[Jim007]

We have the same problem but in addition to the

http://WWW Publishing

Services the FTP Publishing Services also stops. Not using MS Proxy is also not an option for us right now. I would be interested to know if anybody is collecting mail on a POP3 account that is having mail delivery problems in addition to this particular problem.

 

[gaNTuser]

I am having the same problem. We are using NT 4.0 Server with Small Business Server 4.5. We have Microsoft Exchange collecting POP e-mail. Internet access and mail delivery stops when the

http://WWW Publishing

Service goes down. It is happening about once per day.

 

[2know]

After removing an application I though was the problem I found the service still stopped on its own but not as often. At this point I noticed my logs/log files were filling up and that I was running low on disk space. I made "LOTS" of room on the "c" drive and will monitor it from here....

 

[gaNTuser]

We have 350-400 MB free on our Server C: drive. I too was wondering if that was a problem. I'm trying to free up more space to see if that does anything.

 

[cmegha2001]

I have had the same problem... I install MS Proxy Service Pack 1... Problem fixed... the filename at MS Downloads is:

msp2sp1i.exe

 

[gaNTuser]

I installed MS Proxy Service Pack 1 and it seems to have fixed the problem.

Thanks for the tip!