doctorbill
asked on
web ports
I have recently installed SMTPing on my small business server 2003
The installation went without any errors
The server is running IIS and Apache (both are running correctly)
All websites are also running without any problems
When I open the Dashboard for the SMTPing software I get the following error:
http://localhost:33912
The connection to localhost was interrupted
One further point: Thne browser being used is Chromium Portable (installed with the software)
I have checked Listening ports and the 33912 is not listed.
As the address is localhost I cannot imagine that firewall (turned off) / sonicwall is blocking this port
Any suggestions please
The installation went without any errors
The server is running IIS and Apache (both are running correctly)
All websites are also running without any problems
When I open the Dashboard for the SMTPing software I get the following error:
http://localhost:33912
The connection to localhost was interrupted
One further point: Thne browser being used is Chromium Portable (installed with the software)
I have checked Listening ports and the 33912 is not listed.
As the address is localhost I cannot imagine that firewall (turned off) / sonicwall is blocking this port
Any suggestions please
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have just installed the software on another windows xp machine and it is working fine on port 33912 so it looks as if the small business server 2003 is causing the problem
ASKER
I think I know what the problem is:
My Apache server is running on port 888 but the application is trying to use 33912
It looks as if the software installation installed it's own apache server which references port 33912. I will try to change this to 888 in the httpd.conf file
My Apache server is running on port 888 but the application is trying to use 33912
It looks as if the software installation installed it's own apache server which references port 33912. I will try to change this to 888 in the httpd.conf file
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
solved
ASKER