2

Sorry for the bad wording in the title, 'doesn't help' is not allowed as a title, I am definitely able to stop IIS.

While trying to install VisualSVN I ran into the problem that port 443 was already open. After looking through dozens of forum entries and checking netstat (screengrab) I was only able to find out that PID 4 caused the issue, and Process Explorer confirmed the port being listened in the properties window (screengrab).

Now in all those posts Process Explorer was referred to for finding out which service is the culprit, but I cannot really figure out which service in particular opened the port, all I can really see is the listing under TCP/IP. Now I do have IIS installed and plan on setting up websites in the future, for now there is only the default site installed. When I stop the website the listing for port :http and :80 disappear from netstat and Process Explorer, 433 is still there though. Same goes for stopping the entire IIS server in the Manager window or just stopping the IIS service(s).

Is there anything I am doing wrong? Any ideas?

Improve this question

2 Answers 2

Reset to default
3

Do you have routing and remote access service installed? If yes, try to disable it (RRAS uses SSTP by default and it listens for 443 port and lsas.exe process which is using port in your situation is used for IPSEC also).

Improve this answer
9
  • Yes! Finally, that's it, now how can I change the RRAS port from 443 to something else?
    – yspreen
    May 1, 2016 at 11:16
  • Also, do you by any chance have an idea how I can fix the VPN Status page just showing Unavailable at every entry?
    – yspreen
    May 1, 2016 at 11:17
  • If you don't want to remove RRAS role (in case you really need it), disable SSTP port. Go to Routing and Remote access management, choose ports and change available port quantity for SSTP protocol from 128 (default) to 0
    – Senator14
    May 1, 2016 at 11:18
  • @nO_OnE_910 about VPN Status page: I didn't get you full, can you send link to screenshot please?
    – Senator14
    May 1, 2016 at 11:19
  • i.stack.imgur.com/Rh1y6.jpg I dont even have remote access enabled, I just really need the VPN, and it only comes with the remote access.
    – yspreen
    May 1, 2016 at 11:24
1

I think you're going to run into major issues running both IIS and VisualSVN, which installs and runs on Apache, on the exact same server. If I were you, I'd separate them out and give each web server their own VM. I know this doesn't directly answer your question but I'm wondering if your original posted problem is not a symptom of trying to run both web servers on the same VM.

Improve this answer
2
  • well, what problems would that be? All seems to work fine now.
    – yspreen
    May 2, 2016 at 23:06
  • Well I based my original response on the fact that your issue is not a typical experience when installing VisualSVN. The fact that you've had to do some workarounds or troubleshooting means you have conflicts that are not standard. It isn't a stretch to think you won't see other issues down the road as well. Personally, I've just never been a fan of monolithic servers like that which run multiple services. I have all my IIS VMs separate from all my Apache VMs. Also, I would be very concerned about Apache vulnerabilities now exposing threats to your sites that run on IIS and vice versa.
    – Matt Y
    May 5, 2016 at 13:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .