 on server 2003 (32-bit) as a service. It works flawlessly for the most part. After a day or so I begin to have problems. The viewer seems to connect and wait, but the server, as soon as it attempts to connect, closes. (I can telnet and connect to both ports). If I restart the service, the problem goes away.
 on server 2003 (32-bit) as a service. It works flawlessly for the most part. After a day or so I begin to have problems. The viewer seems to connect and wait, but the server, as soon as it attempts to connect, closes. (I can telnet and connect to both ports). If I restart the service, the problem goes away.Some details about my setup.
We only use the repeater once every few days, but will be using a lot more.
I'm using the latest viewer, and the latest single click build that is compatible with vista/7.
I have a .net script on my site for both clients and admins. The admin puts in a support #, and clicks run. The site compiles an exe and sends it to the user.
Same for the client. The client goes to our site, enters a support #, clicks run, and they get the single click packaged exe, that autoruns when launched.
I'm currently testing running the repeater in application mode (not a service), to see what the log says when it starts acting up again.
Any ideas? I saw another user, awhile back, that set their service to restart every few hours. I don't want to do this as it could kill a live connection, and that was a few builds back, so I assume its not the same issue.

