PDA

View Full Version : can i use it with isa server 2004 proxy


cefurkan
04-16-2007, 04:50 PM
well the only open port is 80 at our dormitory
but i want to use programs like bit lord

and the isa server proxy is 192.XXX.X.X

well if it is possible to trick the server at these situations i will buy immediately this program

ty

williameboley
04-16-2007, 05:09 PM
I can not guarantee anything. But I do not see why not.

cefurkan
04-16-2007, 07:14 PM
http://img384.imageshack.us/img384/9746/deneme111uw0.jpg

cefurkan
04-16-2007, 07:16 PM
it doesnt work at bit torrent and bit lord

what shoul i do
i did the proxy setup at internet explorer
127.0.0.1 1080
and my windows firewall and karspersky antivirus is closed

williameboley
04-16-2007, 08:06 PM
Did you set up the Tunnel Client to use Internet Explorer? Are you able to surf the internet?

cefurkan
04-16-2007, 08:09 PM
this program only works for at the prohibited file extensions like as mp3 is prohibited by server but i can download with http

but seems like doesnt work at knight online and all the torrents
i couldnt manage to connect any kind of torrent
i am using proxifier too
so i will probably refund my money but if i could manage to work at least torrents i can use it at least 1 month
actually i need mostly to work knightonline usko
it uses 15100 port
i need help about these problems

williameboley
04-16-2007, 08:11 PM
Let us do 1 thing at a time please. Please answer me. Did you set up Internet Explorer to use the tunnel. Can you surf the internet. You must learn the basics.

cefurkan
04-16-2007, 08:16 PM
well it is very simple
if i can download mp3 from flash get that means i can surfe on the web browser am i right :D

yeah i can surf on the web

williameboley
04-16-2007, 08:22 PM
Have you tried any of the torrent clients that we have guides for? User Guides page http://www.http-tunnel.com/html/support/user_guides.asp
Tips for Newcomers: If you have not already done so please read this post it has a few suggestions on configuration, optimization and trouble shooting. http://forums.http-tunnel.com/showthread.php?t=2145
This may be a useful thread. utorrent http://forums.http-tunnel.com/showthread.php?t=2275&page=4

cefurkan
04-16-2007, 08:28 PM
yeah i have downloaded utorrent pdf
but i could find utorrent 1.6.1
pdf version is 1.6.0
also i tried bitlord
bittorent too

but i used only proxifier not other programs

williameboley
04-16-2007, 09:13 PM
utorrent is natively configurable to use a proxy. You would not need Proxifier. But if you want to use Proxifer then make sure all the programs you want to go through the tunnel are in their default settings and then set up Proxifier to Proxify all + Manually proxify. Make sure you exclude HTTPTunnel. Proxifier Thread, http://forums.http-tunnel.com/showthread.php?p=6586#post6586

cefurkan
04-16-2007, 10:03 PM
i finally managed to connet at bitlord
but here is the ss always rejected by server
i am very close :D

http://img294.imageshack.us/img294/6981/rejectedyj9.jpg

williameboley
04-16-2007, 10:15 PM
You have something configured wrong. I see in your log window the client is trying to connect on 127.0.0.1:1080 you are trying to put the tunnel through the tunnel. Please post a log. Go to the folder you installed the client. Look for HTTPTunneltrace, Open it and make a copy and post it in the forums.

cefurkan
04-17-2007, 09:55 AM
i am not at home at the moment
but surely i will do when i get home

cefurkan
04-17-2007, 12:46 PM
i am parting the log file 4 part
<15 : 39 : 40> HTTP-Tunnel Client v4.4.4000
<15 : 39 : 40> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<15 : 39 : 40> Init: Connecting to Login Server.
<15 : 39 : 40> Retrieving IP Address of HTTP-Tunnel Server...
<15 : 39 : 40> Retrieved High Bandwidth Server IP [209.8.41.148]
<15 : 39 : 40> Available High Bandwidth Servers: 7 [Available Gaming Servers: 2]
<15 : 39 : 41> HTTP/HTTPS/SOCKS 4/SOCKS 5 Servers started on Port 1080
<15 : 39 : 42> Client requesting HTTP URL [cachenetwork.net;/pBanner.aspx]
<15 : 39 : 42> Connection #0: Pinging HTTP-Tunnel Server via HTTP.
<15 : 39 : 42> Upstream connection #0: Time taken for send of 4 bytes upstream : 0.61 seconds
<15 : 39 : 42> Connection #0: Received a HTTP "Pong". Server is alive!
<15 : 39 : 42> Upstream connection #0: setting up connection to 10.1.1.107:1178
<15 : 39 : 42> Upstream connection #0: Initiating upstream connection.
<15 : 39 : 42> Upstream connection #0: Connection Attempt #1[10.1.1.107:1178]
<15 : 39 : 43> Upstream connection #0: Time taken for send of 22 bytes upstream : 0.61 seconds
<15 : 39 : 43> Upstream connection #0: Remote server accepted connection.
<15 : 39 : 43> Upstream connection #0: Time taken for send of 285 bytes upstream : 0.58 seconds
<15 : 39 : 43> Upstream connection #0: sent 285 bytes upstream [0 bytes/0 packets pending];Time taken : 0.59 seconds
<15 : 39 : 46> Configuration successfully updated
<15 : 39 : 46> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<15 : 39 : 46> Init: Connecting to Login Server.
<15 : 39 : 46> Retrieving IP Address of HTTP-Tunnel Server...
<15 : 39 : 46> RetrieveIP: Cached High Bandwidth Server IP [209.8.41.64]
<15 : 39 : 46> RetrieveIP: Log Window Cleared
<15 : 39 : 46> Socks thread #0: Client Application closed connection.
<15 : 39 : 46> Client requesting HTTP URL [cachenetwork.net;/pBanner.aspx]
<15 : 39 : 46> Upstream connection #1: setting up connection to 10.1.1.107:1178
<15 : 39 : 46> Upstream connection #1: Initiating upstream connection.
<15 : 39 : 46> Upstream connection #1: Connection Attempt #1[10.1.1.107:1178]
<15 : 39 : 47> Downstream Socket #0: Completed Header - Size: 128 bytes
<15 : 39 : 47> Downstream Socket #0: Payload piggybacked with header packet: 584 bytes
<15 : 39 : 47> Downstream Socket #0: Connection already terminated, dropping.
<15 : 39 : 47> Upstream connection #0: Time taken for send of 4 bytes upstream : 0.55 seconds
<15 : 39 : 47> Upstream Connection #0: Sent Upstream Thread Closure message.
<15 : 39 : 47> Upstream Connection #0: Upstream data thread dead
<15 : 39 : 47> Upstream connection #1: Time taken for send of 22 bytes upstream : 0.55 seconds
<15 : 39 : 47> Upstream connection #1: Remote server accepted connection.
<15 : 39 : 47> Upstream connection #1: Time taken for send of 446 bytes upstream : 0.58 seconds
<15 : 39 : 47> Upstream connection #1: sent 446 bytes upstream [0 bytes/0 packets pending];Time taken : 0.58 seconds
<15 : 40 : 06> Client requesting HTTP URL [www.torrentpond.com;/]
<15 : 40 : 06> Upstream connection #2: setting up connection to 10.1.1.107:1178
<15 : 40 : 06> Upstream connection #2: Initiating upstream connection.
<15 : 40 : 06> Upstream connection #2: Connection Attempt #1[10.1.1.107:1178]
<15 : 40 : 07> Upstream connection #2: Remote server accepted connection.
<15 : 40 : 47> Downstream socket #1 closed [1 times], attempting to reconnect.
<15 : 40 : 48> Downstream Socket #1: TunnelServer msg - Remote Host Closed Connection.
<15 : 40 : 48> Client requesting HTTP URL [cachenetwork.net;/v44PaidBanner.JPG]
<15 : 40 : 48> Upstream connection #3: setting up connection to 10.1.1.107:1178
<15 : 40 : 48> Upstream connection #3: Initiating upstream connection.
<15 : 40 : 48> Upstream connection #3: Connection Attempt #1[10.1.1.107:1178]
<15 : 40 : 49> Upstream connection #3: Remote server accepted connection.
<15 : 40 : 49> Upstream Connection #1: Sent Upstream Thread Closure message.
<15 : 40 : 49> Upstream Connection #1: Upstream data thread dead
<15 : 40 : 58> Configuration successfully updated
<15 : 40 : 58> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<15 : 40 : 58> Init: Connecting to Login Server.
<15 : 40 : 58> Retrieving IP Address of HTTP-Tunnel Server...
<15 : 40 : 58> RetrieveIP: Cached High Bandwidth Server IP [209.8.41.212]
<15 : 40 : 59> Socks thread #3: Client Application closed connection.
<15 : 40 : 59> Client requesting HTTP URL [cachenetwork.net;/v44PaidBanner.JPG]
<15 : 40 : 59> Upstream connection #4: setting up connection to 10.1.1.107:1178
<15 : 40 : 59> Upstream connection #4: Initiating upstream connection.
<15 : 40 : 59> Upstream connection #4: Connection Attempt #1[10.1.1.107:1178]
<15 : 40 : 59> Upstream Connection #3: Sent Upstream Thread Closure message.
<15 : 40 : 59> Upstream Connection #3: Upstream data thread dead
<15 : 40 : 59> Upstream connection #4: Remote server accepted connection.

cefurkan
04-17-2007, 12:47 PM
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 04> Connection Test: HTTP Error 404. Please contact Technical Support.
<15 : 41 : 04> Connection Test: Trying next login Server.
<15 : 41 : 05> Connection Test: All login Servers inaccessible, Connection Test Failed.
<15 : 41 : 07> Downstream socket #2 closed [1 times], attempting to reconnect.
<15 : 41 : 07> SOCKS Server thread #5: SOCKS 5 handshake done, waiting for command.
<15 : 41 : 07> Client requesting SOCKS5CONNECT to 127.0.0.1:1080
<15 : 41 : 07> Application requesting connection to localhost, rerouted through HTTP-Tunnel.
<15 : 41 : 07> Client requesting HTTP URL [www.torrentpond.com;/side.html?q=&enginenum=]
<15 : 41 : 07> Upstream connection #5: setting up connection to 10.1.1.107:1178
<15 : 41 : 07> Upstream connection #5: Initiating upstream connection.
<15 : 41 : 07> Upstream connection #5: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 07> SOCKS Server thread #6: SOCKS 5 handshake done, waiting for command.
<15 : 41 : 07> Client requesting SOCKS5CONNECT to 127.0.0.1:1080
<15 : 41 : 07> Application requesting connection to localhost, rerouted through HTTP-Tunnel.
<15 : 41 : 07> Client requesting HTTP URL [www.torrentpond.com;/blank.html]
<15 : 41 : 07> Upstream connection #6: setting up connection to 10.1.1.107:1178
<15 : 41 : 07> Upstream connection #6: Initiating upstream connection.
<15 : 41 : 07> Upstream connection #6: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 08> Downstream Socket #2: TunnelServer msg - Remote Host Closed Connection.
<15 : 41 : 08> SOCKS Server thread #7: SOCKS 5 handshake done, waiting for command.
<15 : 41 : 08> Client requesting SOCKS5CONNECT to 127.0.0.1:1080
<15 : 41 : 08> Application requesting connection to localhost, rerouted through HTTP-Tunnel.
<15 : 41 : 08> Client requesting HTTP URL [www.google-analytics.com;/__utm.gif?utmwv=1&utmn=1491604072&utmcs=iso-8859-1&utmsr=1024x768&utmsc=16-bit&utmul=tr&utmje=1&utmfl=9.0&utmdt=TorrentPond.com%20-%20Search%20ALL%20Torrent%20Engines%20Here&utmhn=www.torrentpond.com&utmr=-&utmp=/&utmac=UA-257720-3&utmcc=__utma%3D161092152.1766249490.1175616509.117 6749999.1176813668.5%3B%2B__utmb%3D161092152%3B%2B __utmc%3D161092152%3B%2B__utmz%3D161092152.1175616 509.1.1.utmccn%3D(direct)%7Cutmcsr%3D(direct)%7Cut mcmd%3D(none)%3B%2B]
<15 : 41 : 08> Upstream connection #7: setting up connection to 10.1.1.107:1178
<15 : 41 : 08> Upstream connection #7: Initiating upstream connection.
<15 : 41 : 08> Upstream connection #7: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 08> Upstream connection #5: Remote server accepted connection.
<15 : 41 : 08> Upstream connection #6: Remote server accepted connection.
<15 : 41 : 08> Upstream connection #7: Remote server accepted connection.
<15 : 41 : 09> Upstream Connection #2: Sent Upstream Thread Closure message.
<15 : 41 : 09> Upstream Connection #2: Upstream data thread dead
<15 : 41 : 16> Configuration successfully updated
<15 : 41 : 16> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<15 : 41 : 16> Init: Connecting to Login Server.
<15 : 41 : 16> Retrieving IP Address of HTTP-Tunnel Server...
<15 : 41 : 16> RetrieveIP: Cached High Bandwidth Server IP [209.8.41.64]
<15 : 41 : 16> RetrieveIP: Log Window Cleared
<15 : 41 : 16> Socks thread #4: Client Application closed connection.
<15 : 41 : 16> Client requesting HTTP URL [cachenetwork.net;/v44PaidBanner.JPG]
<15 : 41 : 16> Upstream connection #8: setting up connection to 10.1.1.107:1178
<15 : 41 : 16> Upstream connection #8: Initiating upstream connection.
<15 : 41 : 16> Upstream connection #8: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 17> Upstream Connection #4: Sent Upstream Thread Closure message.
<15 : 41 : 17> Upstream connection #8: Remote server accepted connection.
<15 : 41 : 17> Upstream Connection #4: Upstream data thread dead
<15 : 41 : 21> SOCKS Server thread #9: SOCKS 5 handshake done, waiting for command.
<15 : 41 : 21> Client requesting SOCKS5CONNECT to 127.0.0.1:1080
<15 : 41 : 21> Application requesting connection to localhost, rerouted through HTTP-Tunnel.
<15 : 41 : 21> Client requesting HTTP URL [www.http-tunnel.com;/]
<15 : 41 : 21> Upstream connection #9: setting up connection to 10.1.1.107:1178
<15 : 41 : 21> Upstream connection #9: Initiating upstream connection.
<15 : 41 : 21> Upstream connection #9: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 21> Upstream connection #9: Remote server accepted connection.
<15 : 41 : 38> SOCKS Server thread #10: SOCKS 5 handshake done, waiting for command.
<15 : 41 : 38> Client requesting SOCKS5CONNECT to 127.0.0.1:1080
<15 : 41 : 38> Application requesting connection to localhost, rerouted through HTTP-Tunnel.
<15 : 41 : 38> Client requesting HTTP URL [www.google.com.tr;/]
<15 : 41 : 38> Connection #10: Pinging HTTP-Tunnel Server via HTTP.
<15 : 41 : 39> Connection #10: Received a HTTP "Pong". Server is alive!
<15 : 41 : 39> Upstream connection #10: setting up connection to 10.1.1.107:1178
<15 : 41 : 39> Upstream connection #10: Initiating upstream connection.
<15 : 41 : 39> Upstream connection #10: Connection Attempt #1[10.1.1.107:1178]
<15 : 41 : 39> Upstream connection #10: Remote server accepted connection.
<15 : 41 : 41> Downstream socket #10 closed [1 times], attempting to reconnect.
<15 : 41 : 41> Downstream Socket #10: TunnelServer msg - Remote Host Closed Connection.
<15 : 41 : 42> Upstream Connection #10: Sent Upstream Thread Closure message.
<15 : 41 : 42> Upstream Connection #10: Upstream data thread dead
<15 : 41 : 52> Socks thread #9: Client Application closed connection.
<15 : 41 : 52> Upstream Connection #9: Sent Upstream Thread Closure message.
<15 : 41 : 52> Upstream Connection #9: Upstream data thread dead

cefurkan
04-17-2007, 12:51 PM
i think this part is most importatn for u
and i added attachment of log file this post



<15 : 42 : 10> Client requesting SOCKS5CONNECT to 219.95.196.93:21087
<15 : 42 : 10> Connection #40: Received a HTTP "Pong". Server is alive!
<15 : 42 : 10> Upstream connection #20: Remote server accepted connection.
<15 : 42 : 10> Upstream connection #30: setting up connection to 201.235.9.35:25602
<15 : 42 : 10> Upstream connection #30: Initiating upstream connection.
<15 : 42 : 10> Upstream connection #30: Connection Attempt #1[201.235.9.35:25602]
<15 : 42 : 10> SOCKS Server thread #42: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 10> Client requesting SOCKS5CONNECT to 62.30.227.44:63743
<15 : 42 : 10> SOCKS Server thread #43: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 10> Client requesting SOCKS5CONNECT to 212.13.50.187:24690
<15 : 42 : 11> Upstream connection #30: Remote server accepted connection.
<15 : 42 : 11> SOCKS Server thread #44: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 11> Client requesting SOCKS5CONNECT to 83.223.146.178:21934
<15 : 42 : 11> Upstream connection #36: setting up connection to 80.203.119.81:54025
<15 : 42 : 11> Upstream connection #36: Initiating upstream connection.
<15 : 42 : 11> Upstream connection #36: Connection Attempt #1[80.203.119.81:54025]
<15 : 42 : 11> SOCKS Server thread #45: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 11> Client requesting SOCKS5CONNECT to 212.200.146.115:20421
<15 : 42 : 11> Upstream connection #33: Remote server accepted connection.
<15 : 42 : 11> SOCKS Server thread #46: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 11> Client requesting SOCKS5CONNECT to 88.232.190.152:43702
<15 : 42 : 12> SOCKS Server thread #47: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 12> Client requesting SOCKS5CONNECT to 58.108.52.47:35160
<15 : 42 : 12> SOCKS Server thread #48: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 12> Client requesting SOCKS5CONNECT to 208.101.70.198:23623
<15 : 42 : 12> SOCKS Server thread #49: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 12> Client requesting SOCKS5CONNECT to 62.162.224.172:7295
<15 : 42 : 13> SOCKS Server thread #50: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 13> Client requesting SOCKS5CONNECT to 161.53.95.5:59715
<15 : 42 : 13> Connection #50: Pinging HTTP-Tunnel Server via HTTP.
<15 : 42 : 13> SOCKS Server thread #51: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 13> Client requesting SOCKS5CONNECT to 209.8.41.67:18801
<15 : 42 : 13> Connection #50: Received a HTTP "Pong". Server is alive!
<15 : 42 : 13> SOCKS Server thread #52: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 13> Client requesting SOCKS5CONNECT to 84.255.241.118:11234
<15 : 42 : 14> SOCKS Server thread #53: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 14> Client requesting SOCKS5CONNECT to 193.40.10.218:12257
<15 : 42 : 14> SOCKS Server thread #54: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 14> Client requesting SOCKS5CONNECT to 66.100.227.229:23206
<15 : 42 : 14> SOCKS Server thread #55: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 14> Client requesting SOCKS5CONNECT to 68.35.105.64:6881
<15 : 42 : 15> SOCKS Server thread #56: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 15> Client requesting SOCKS5CONNECT to 84.41.81.118:51969
<15 : 42 : 15> SOCKS Server thread #57: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 15> Client requesting SOCKS5CONNECT to 85.95.109.230:6881
<15 : 42 : 15> SOCKS Server thread #58: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 15> Client requesting SOCKS5CONNECT to 24.183.51.143:23189
<15 : 42 : 16> SOCKS Server thread #59: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 16> Client requesting SOCKS5CONNECT to 71.109.65.130:62576
<15 : 42 : 16> SOCKS Server thread #60: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 16> Client requesting SOCKS5CONNECT to 68.252.226.203:6881
<15 : 42 : 16> Connection #60: Pinging HTTP-Tunnel Server via HTTP.
<15 : 42 : 16> SOCKS Server thread #61: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 16> Client requesting SOCKS5CONNECT to 137.186.177.4:27369
<15 : 42 : 16> Connection #60: Received a HTTP "Pong". Server is alive!
<15 : 42 : 17> SOCKS Server thread #62: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 17> Client requesting SOCKS5CONNECT to 71.249.36.144:40161
<15 : 42 : 17> SOCKS Server thread #63: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 17> Client requesting SOCKS5CONNECT to 63.246.166.183:6881
<15 : 42 : 17> Downstream socket #8 closed [1 times], attempting to reconnect.
<15 : 42 : 17> SOCKS Server thread #64: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 17> Client requesting SOCKS5CONNECT to 190.51.33.69:17764
<15 : 42 : 18> SOCKS Server thread #65: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 18> Client requesting SOCKS5CONNECT to 68.3.143.7:19408
<15 : 42 : 18> Downstream Socket #8: TunnelServer msg - Remote Host Closed Connection.
<15 : 42 : 18> SOCKS Server thread #66: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 18> Client requesting SOCKS5CONNECT to 150.250.183.161:20239
<15 : 42 : 18> SOCKS Server thread #67: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 18> Client requesting SOCKS5CONNECT to 88.208.94.2:9687
<15 : 42 : 18> Upstream Connection #8: Sent Upstream Thread Closure message.
<15 : 42 : 18> Upstream Connection #8: Upstream data thread dead
<15 : 42 : 19> SOCKS Server thread #68: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 19> Client requesting SOCKS5CONNECT to 218.212.58.49:12936
<15 : 42 : 19> SOCKS Server thread #69: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 19> Client requesting SOCKS5CONNECT to 200.157.23.39:11766
<15 : 42 : 19> SOCKS Server thread #70: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 19> Client requesting SOCKS5CONNECT to 74.105.245.124:61501
<15 : 42 : 19> Connection #70: Pinging HTTP-Tunnel Server via HTTP.
<15 : 42 : 20> SOCKS Server thread #71: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 20> Client requesting SOCKS5CONNECT to 203.87.130.245:65102
<15 : 42 : 20> Connection #70: Received a HTTP "Pong". Server is alive!
<15 : 42 : 20> SOCKS Server thread #72: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 20> Client requesting SOCKS5CONNECT to 83.102.16.69:25671
<15 : 42 : 21> SOCKS Server thread #73: SOCKS 5 handshake done, waiting for command.
<15 : 42 : 21> Client requesting SOCKS5CONNECT to 209.169.159.140:6881
<15 : 42 : 22> Socks thread #27: Client Application closed connection.
<15 : 42 : 23> Upstream Connection #27: Upstream data thread dead
<15 : 42 : 25> Upstream connection #14: Remote server rejected connection.
<15 : 42 : 25> Upstream connection #66: setting up connection to 150.250.183.161:20239
<15 : 42 : 25> Upstream connection #66: Initiating upstream connection.
<15 : 42 : 25> Upstream connection #66: Connection Attempt #1[150.250.183.161:20239]
<15 : 42 : 26> Upstream connection #19: Remote server rejected connection.
<15 : 42 : 26> Upstream connection #52: setting up connection to 84.255.241.118:11234
<15 : 42 : 26> Upstream connection #52: Initiating upstream connection.
<15 : 42 : 26> Upstream connection #52: Connection Attempt #1[84.255.241.118:11234]
<15 : 42 : 26> Upstream connection #21: Remote server rejected connection.
<15 : 42 : 27> Upstream connection #56: setting up connection to 84.41.81.118:51969
<15 : 42 : 27> Upstream connection #56: Initiating upstream connection.
<15 : 42 : 27> Upstream connection #56: Connection Attempt #1[84.41.81.118:51969]
<15 : 42 : 27> Upstream connection #23: Remote server rejected connection.
<15 : 42 : 27> Upstream connection #42: setting up connection to 62.30.227.44:63743
<15 : 42 : 27> Upstream connection #42: Initiating upstream connection.
<15 : 42 : 27> Upstream connection #42: Connection Attempt #1[62.30.227.44:63743]
<15 : 42 : 27> Upstream connection #24: Remote server rejected connection.
<15 : 42 : 27> Upstream connection #57: setting up connection to 85.95.109.230:6881
<15 : 42 : 27> Upstream connection #57: Initiating upstream connection.
<15 : 42 : 27> Upstream connection #57: Connection Attempt #1[85.95.109.230:6881]
<15 : 42 : 28> Upstream connection #42: Remote server accepted connection.
<15 : 42 : 28> Upstream connection #52: Remote server rejected connection.
<15 : 42 : 28> Upstream connection #70: setting up connection to 74.105.245.124:61501
<15 : 42 : 28> Upstream connection #70: Initiating upstream connection.
<15 : 42 : 28> Upstream connection #70: Connection Attempt #1[74.105.245.124:61501]
<15 : 42 : 28> Upstream connection #64: setting up connection to 190.51.33.69:17764
<15 : 42 : 28> Upstream connection #64: Initiating upstream connection.
<15 : 42 : 28> Upstream connection #64: Connection Attempt #1[190.51.33.69:17764]
<15 : 42 : 32> Upstream connection #36: Remote server rejected connection.
<15 : 42 : 32> Upstream connection #49: setting up connection to 62.162.224.172:7295
<15 : 42 : 32> Upstream connection #49: Initiating upstream connection.
<15 : 42 : 32> Upstream connection #49: Connection Attempt #1[62.162.224.172:7295]

cefurkan
04-17-2007, 01:00 PM
well i cleared the log file and setup gettin logs level 5
then opene first bitlord

after knight online
both of them i get same error
request rejected by server or something like that

here is the logs attached

williameboley
04-17-2007, 01:06 PM
Please tell me something about your set-up. OS What torrent client are you using? Is it natively configurable to use a proxy or are you SOCKsing it? Tell me how you have your torrnent client configured. Edit: you can get utorrent 1.6.0 here: http://oldversion.com/program.php?n=utorrent

cefurkan
04-17-2007, 01:17 PM
well it started downloading

now i am getting 10 kybt second
but there is no upload(this may cause some problems i think)

i am using bit lord
i made its proxy settings
socks 5
localhost 1080
i have only karspersky and windows firewall both of them is closed
my operations system is windows xp with sp2

but knight online is still doesnt work

knight online port is 15100

cefurkan
04-17-2007, 01:19 PM
well upload started too

i think the only left problem is knightonline (it was my ultimate aim to buy this program)


could u help me about to connect knightonline

williameboley
04-17-2007, 01:21 PM
Congrats. Sometimes things just need to settle down before a torrnet client is happy. I personally don't use torrent clients. I have dreadful luck. I can get them to work but I never seem to have files that anyone else wants. What? Hey, I like Wayne Newton. :p I use LimeWire I can get most any file I want. I also use LimeWire to download torrents. KOL may not be as easy if it is not natively configurable Can you configure KOL to use a proxy?

cefurkan
04-17-2007, 01:50 PM
do wow have settings for proxy

kol doesnt have

cefurkan
04-17-2007, 02:07 PM
i get the message remote server rejected connection a lot is it normal and
remote host closed connection

is it normal to get these messages a lot ?

williameboley
04-17-2007, 02:51 PM
For any P2P Client yes. You will get loads of those. For KOL you will need to use a Proxifying Agent ( Proxifier, HummingBird, etc ). There are various ones, you can find links and guides to configure those. If you will dedicate yourself to this you may be able to get it to work. Some get discouraged because it is not like turning on a light switch so they give up. You may need to teach yourself something. HTTPTunnel Support will do all it can to assist you. My first suggestion is to use either Proxifier or HummingBird ( HummingBird is free ) set either to Proxify/SOCKS all. Make sure all programs you want to use the tunnel are in their default settings. Additionally, Make sure you exclude the tunnel client from the Proxify/SOCKS list in either Proxifier or HummingBird. All these links are relevant, please be sure to visit each: User Guides page http://www.http-tunnel.com/html/support/user_guides.asp
Proxifier Thread, http://forums.http-tunnel.com/showthread.php?p=6586#post6586
HummingBird: http://forums.http-tunnel.com/showthread.php?t=2303
Tips for Newcomers: If you have not already done so please read this post it has a few suggestions on configuration, optimization and trouble shooting. http://forums.http-tunnel.com/showthread.php?t=2145

cefurkan
04-17-2007, 06:36 PM
look at this i think u are thinking what i think
isa server admin has blocked http-tunnel seems like



<21 : 30 : 07> HTTP-Tunnel Client v4.4.4000
<21 : 30 : 07> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<21 : 30 : 07> Init: Connecting to Login Server.
<21 : 30 : 07> Retrieving IP Address of HTTP-Tunnel Server...
<21 : 30 : 08> Retrieved High Bandwidth Server IP [209.8.41.32]
<21 : 30 : 08> Available High Bandwidth Servers: 7 [Available Gaming Servers: 2]
<21 : 30 : 09> HTTP/HTTPS/SOCKS 4/SOCKS 5 Servers started on Port 1080
<21 : 30 : 21> Configuration successfully updated
<21 : 30 : 21> Configuration: User Specified as Proxy - no Auth [192.168.0.1:8080]
<21 : 30 : 21> Init: Connecting to Login Server.
<21 : 30 : 21> Retrieving IP Address of HTTP-Tunnel Server...
<21 : 30 : 21> RetrieveIP: Cached High Bandwidth Server IP [209.8.41.64]
<21 : 30 : 21> RetrieveIP: Log Window Cleared
<21 : 31 : 08> SOCKS Server thread #0: SOCKS 5 handshake done, waiting for command.
<21 : 31 : 08> Client requesting SOCKS5CONNECT to 87.236.194.96:6969
<21 : 31 : 08> Connection #0: Pinging HTTP-Tunnel Server via HTTP.
<21 : 31 : 12> Connection #0: Received a HTTP "Pong". Server is alive!
<21 : 31 : 12> Upstream connection #0: setting up connection to 87.236.194.96:6969
<21 : 31 : 12> Upstream connection #0: Initiating upstream connection.
<21 : 31 : 12> Upstream connection #0: Connection Attempt #1[87.236.194.96:6969]
<21 : 31 : 15> Upstream connection #0: Remote server accepted connection.
<21 : 31 : 15> Downstream Socket #0: unexpected response -> dumped to file DownHeaderDump.txt.
<21 : 31 : 15> DownStream Socket #0: HTTP Error from proxy/HTTP-Tunnel server: HTTP/1.1 502 Proxy E
<21 : 31 : 15> DownStream Socket #0: Debug Info: HTTP/1.1 502 PROXY E
<21 : 31 : 20> SOCKS Server thread #1: SOCKS 5 handshake done, waiting for command.
<21 : 31 : 20> Client requesting SOCKS5CONNECT to 87.236.194.96:6969
<21 : 31 : 20> Upstream connection #1: setting up connection to 87.236.194.96:6969
<21 : 31 : 20> Upstream connection #1: Initiating upstream connection.
<21 : 31 : 20> Upstream connection #1: Connection Attempt #1[87.236.194.96:6969]
<21 : 31 : 23> Upstream Connection #0: Sent Upstream Thread Closure message.
<21 : 31 : 23> Upstream Connection #0: Upstream data thread dead
<21 : 31 : 24> Upstream connection #1: Remote server accepted connection.
<21 : 31 : 24> Downstream Socket #1: unexpected response -> dumped to file DownHeaderDump.txt.
<21 : 31 : 24> DownStream Socket #1: HTTP Error from proxy/HTTP-Tunnel server: HTTP/1.1 502 Proxy E
<21 : 31 : 24> DownStream Socket #1: Debug Info: HTTP/1.1 502 PROXY E
<21 : 31 : 34> Upstream Connection #1: Sent Upstream Thread Closure message.
<21 : 31 : 34> Upstream Connection #1: Upstream data thread dead

williameboley
04-17-2007, 07:15 PM
What application are you using? Is this KOL? I do not believe you are being blocked you are able to surf and use your torrent client.

cefurkan
04-17-2007, 07:25 PM
no i cant do anything now
this has happened from this evening :D

i cant even surf on the net now

i thought the program developers found a way to be invisible or maybe seeing as surfing on the google instead of http tunnel data transfer on the server
but seems like they didnt think about it

cefurkan
04-17-2007, 07:29 PM
is there any way to pass this
if there isnt i have to refund my money :(

williameboley
04-17-2007, 07:59 PM
Configure Internet Explorer to use the SOCKS method see if that makes a difference.

cefurkan
04-17-2007, 09:00 PM
Configure Internet Explorer to use the SOCKS method see if that makes a difference.

well doesnt work

williameboley
04-17-2007, 09:33 PM
I would try this: In Internet Explorer make suure Use HTTP 1.1 through proxy connections" option is enabled/disabled close IE and start it again. You find that in>Tools>Internet Options>Advanced>scroll until you find it, disable and restart. Also see if you have Proxy supports connect command. check/uncheck and try that.

cefurkan
04-18-2007, 10:42 AM
well doesnt work


so say ur developers that
make their program invisible or seems like different connection at isa server
otherwise u lose more customers like me :d
i am complety restricted from server when i try to connect with http-tunnel

williameboley
04-18-2007, 11:54 AM
I regret I was not able to assist you better. Be sure to request your refund as soon as possible. I do not think your trial period has expired. I am intrigued however that it was working and then stopped: I can not help but think that if your surmise is correct that maybe if I had suggested the SOCKS method as your initial configuration they may not have seen HTTPTunnel. In the HTTP mode HTTPTunnel is seen as a proxy server, in the SOCKS mode the same IP is visible but not listed as a proxy server. Although what ever cache your network may use it may not permit anonymous IP connections. This is pure speculation though.

cefurkan
04-18-2007, 09:05 PM
well i send my accaunt cancellation request
and here is the error that i have encountered
if somebody else encounter this as fast as he can do submit his cancellation

http://img411.imageshack.us/img411/2632/bigproblemst7.jpg