search for: tcpview

...an't connect to another tinc, both windows. The error displayed is: Timeout from name (ipaddress port number) during authentication I can connect to the ipaddress on the port with telnet - no problem. The wierd thing is: *all* programs that connect to internet display the proxy ip address in TCPView as the remote end point. Telnet included. tinc on the other hand displays *real* ip address there. This is kind of strange because how I understand how isa winsock proxy client works is by substituting the winsock dlls and transparently redirecting all calls to the proxy. I have no idea why this d...

Already try the pre realease 0.3. The rtpeer.rb is working. But I don''t know why is take quite a while to listen only port 6969. The after that start to scan port 6881,6882..etc. After that manage to download the file normally. As usual I run everything in one PC. Azureus, ABC, and rubytorrent. The example on "doc\api.txt" still doesn''t work for me. I am very hapy the

...n 10 listen-socket ports. I have 44 streams that I'm trying to relay via Icecast. It works just fine until I try to add the listen-socket port definitions. If I put the 11th one in, it will crash on startup without entering anything in the log files (log level on 4). I've use sysinternal tcpView to verify that the ports I'm trying to use are open and they are. Any ideas anyone???? Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Tuesday, July 19, 2005 11:17 AM To: 'icecast' Subject: RE: [Icecast] relaying IceCast from ShoutCast Ok, Foun...

...: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) pops out. It does not exit, however, and I must kill the process using task manager. I am syncing a few directories to my backup hard drive, which is local. There's no remote network access going on that I know of. Using tcpview from sysinternals.com, I can see that when a process "hangs", its ports are still open. When I get a clean exit, all ports are closed. I ran it a few times with strace, and the ones that got stuck seemed to be in a loop and calling "select" a lot. I've been more successfu...

...time and haven't rebooted my PC for a while now (maybe that could fix it?). But the bug exists. $ env | grep SSH SSH_AGENT_PID=3244 SSH_AUTH_SOCK=/tmp/ssh-wA0SC8jY0Y/agent.3372 Content of file: /tmp/ssh-wA0SC8jY0Y/agent.3372 !<socket >2436 s 4E6A720D-ED8DF735-4D2422B5-0FA6178C >From TCPView I see that process ssh-agent:3244 is listening on UDP port 2437 (not 2436!) Could this be the problem, that the port number is off by one? Here some output from TCP Spy that could be useful: (?) the next process to start and make a socket call will be spyed process attached, command line='C...

...n 10 listen-socket ports. I have 44 streams that I'm trying to relay via Icecast. It works just fine until I try to add the listen-socket port definitions. If I put the 11th one in, it will crash on startup without entering anything in the log files (log level on 4). I've use sysinternal tcpView to verify that the ports I'm trying to use are open and they are. Any ideas anyone???? Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Tuesday, July 19, 2005 11:17 AM To: 'icecast' Subject: RE: [Icecast] relaying IceCast from ShoutCast Ok, Found...