Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just read this article which I find concerning:

"After 90 minutes of troubleshooting, Nash traced the problem to TeamViewer, which he used to remotely administer the client's servers. It turns out the program had opened up its own webserver on the client's machine as soon as Apache went down and in the process made it impossible for the client, a large provider of business software, to restart its proper website."

I started using TeamViewer recently because it's just much better than UltraVNC (runs on both XP and Vista, the server dials out instead of requiring the user to open a port on their router + better performance than UVNC)... but I thought that TeamViewer had both the server and client connect out to TV's web server for data to flow between the two hosts.

Why does TV even need to open a web server on the server host?

share|improve this question
up vote 3 down vote accepted

Ports 80 and 5938 are used by default for TeamViewer's DirectIn -feature, which enables faster connection openings by trying to configure a NAT route automatically by using UPnP.

You can disable the DirectIn performance optimizations from TeamViewer's options menu in Extras -> Options -> Advanced -> Show advanced options and by unchecking the "Enable DirectIn Performance optimization".

share|improve this answer
Thanks guys. I'll check LogMeIn to see what it looks like. – OverTheRainbow Aug 4 '09 at 9:30
Does not work for me – Ilya Kochetov Nov 8 '10 at 8:46

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.