Author Topic: team viewer cycling through ports  (Read 6798 times)

ordrdrk

  • Newbie
  • *
  • Posts: 4
team viewer cycling through ports
« on: January 19, 2012, 09:50:56 AM »
I installed TV7 last Saturday and everything worked fine.  Today (with a PC restart since last Saturday), when I try to start TV I don't get anything.  Checking the log file, it appears that TV is cycling through thousands of ports.  I'm seeing thousands of measages like:

2012/01/19 10:45:01.890  4708  5148 S0!! CInterProcessNetwork::Start(): Port 6350 is in use. Trying next port

I'm using Windows 7 64-bit.  I've tried uninstalling, rebooting, and re-installing but that doesn't change anything.  Any ideas?

Denis

matt

  • Hero Member
  • *****
  • Posts: 904
Re: team viewer cycling through ports
« Reply #1 on: January 19, 2012, 10:10:14 AM »
Have you selected to NOT use port 80 in the options?

ordrdrk

  • Newbie
  • *
  • Posts: 4
Re: team viewer cycling through ports
« Reply #2 on: January 19, 2012, 11:09:35 AM »
How do you specify options?

ordrdrk

  • Newbie
  • *
  • Posts: 4
Re: team viewer cycling through ports
« Reply #3 on: January 19, 2012, 11:21:25 AM »
Poking around, it looks like you can specify not use port 80 when you get the screen after startup.  Unfortunately, I never get a screen (I did last week when it was working) so I have no way to set options.

ordrdrk

  • Newbie
  • *
  • Posts: 4
Re: team viewer cycling through ports
« Reply #4 on: January 19, 2012, 11:50:26 AM »
OK, now the problem has cleared up.  The TV service was continually searching for a port and I couldn't even stop the process.  So I tried rebooting (again) and when I checked the log file it said it had port 5938.  Then I started the command and got a login screen whereas before I got nothing.

Interesting, I was having a problem starting up my Apache server which uses port 80.  It wouldn't start even though netstat didn't show port 80 being used by anybody.  So I was trying to get TV going so I could have someone else check what the problem with Apache was.  Once I saw TV working after my reboot I tried starting the Apache server again and it worked.

So it appears likely that these two problems - Apache and TV - were related and maybe there was something hokey with port 80 that caused this.  Whatever the problem was appears to have cleared up for now.