Problem with Repeater 1.1.0.7 crashing

[cynagen]

Hey, let me just go ahead and explain how I got to this point.

First thing's first, I work as tech support, and got sick of the software we had here to remote connect to customer's computers. So I came up with and started using the SingleClick in combination with Repeater Mode II to identify customers by their unique ticket numbers whenever they open a new issue with us. Now, when I was first deploying it among the rest of the group, we had an issue with 1.1.0.4 crashing all the time, prematurely ending connections on the pretense of "EOF". We replaced 1.1.0.4 with 1.1.0.7, and all has been well for a while. Now we're starting to see more and more frequent crashes of 1107. Has anybody else been experiencing this? Getting called at 10am on one of my days off while trying to sleep in, is never fun, need to find a solution for this and fast, boss man isn't happy.

[redge]

Is'nt problem of your computer hosting repeater memory/hard drive failure/too warm computer ?
Check the event log of your windows computer hosting repeater.
not the log of repeater.

Then,
usel free public tools for test hardware (mainboard/hard disk tools)
http://www.ultimatebootcd.com


If there really serious issue you described, I think we have a lots of complaints coming since released december 2005, but I don't see anything until your post.


stop repeater,
delete settings.txt,
start repeater,
configure the repeater... Save
stop repeater
start repeater
try again SC and vncviewer trough your repeater

and check there no software using same 2 ports of your repeater you set.
tcpview free from sysinternals conflicts after fews min/hours ?
http://download.sysinternals.com/Files/TdiMonNt.zip
http://www.sysinternals.com/Utilities/TcpView.html

[cynagen]

Naw, we have a dedicated server room that stays in the 70s at all times, so the machine isn't getting too warm, as for eating up lots of memory, has anyone seen the repeater have a memory leak perhaps? Or continue to hold onto the memory needed for a connection after it was disconnected, causing it to just keep taking memory till it crashes cause there's no more? Anyone seen that scenario? Either an inadequacy in the system or something in the software is buggy, and the 1.1.0.4 had the same issues, only a lot lot sooner. We're moving the server to another more reliable machine, and we're going to see what we end up with after this.

[cynagen]

So far so good, still not sure, but the boss states that the server still is running when he checks on it, just that it's not getting any connections in from what it appears. So maybe it's a port locking issue? We'll see.

[redge]

could you try this alternative release repeater 1.2.2.1 ?
before try, read the last post of the url below:
[topic=5601][/topic]