| Author | Message | Time |
|---|---|---|
| Beastfromteheast | Hello, I am trying to get my bot to connect to a trade channel on a realm server through a proxy. However, no matter what proxy i try (which have been tested working) I never make it into the channel. I correctly specified socks4/5 in the menu and I am certain I typed the address in correctly. Does anyone have any ideas on how I can get it to connect or have a proxy I can try which they have successfully connected with? thanks -Beast | March 8, 2006, 10:50 PM |
| Kp | Does the SOCKS server return an error code? If not, what's the last message that battle.net sends you? It's possible you're not logging in correctly. Your wording implies that you don't belong here, but I'm going to give you the benefit of the doubt and prompt you as though you're just clueless about debugging. | March 9, 2006, 3:01 AM |
| Beastfromteheast | This is the message I'm getting. [1:01:46 AM] [BNLS] Connecting... [1:01:46 AM] [BNLS] Connected! [1:01:46 AM] [BNLS] Authorized! [1:01:46 AM] [PROXY] Connecting... [1:01:46 AM] [PROXY] Connected! [1:01:47 AM] [PROXY] 10053 -- Connection is aborted due to timeout or other failure [1:01:47 AM] [PROXY] Disconnected. [1:01:47 AM] All connections closed. [1:01:47 AM] [PROXY] The Battle.net server has terminated your connection. [1:01:47 AM] [PROXY] Attempting to reconnect... | March 9, 2006, 6:04 AM |
| MyStiCaL | Well, Im guessing your proxie is bad and/or (IPBanned) wouldn't you? | March 9, 2006, 6:07 AM |
| HeRo | 61.183.37.227:1080 222.90.76.140:1080 60.191.41.125:1080 24.244.130.199:1080 203.76.188.125:1080 61.17.104.4:1080 201.252.52.159:1080 168.115.120.146:1080 202.149.219.214:1080 203.187.235.106:1080 200.126.186.180:1080 203.187.205.111:1080 203.187.222.121:1080 61.191.251.18:1080 210.211.172.175:1080 200.168.22.82:1080 219.72.230.2:1080 210.211.173.20:1080 202.68.133.186:1080 83.100.140.98:1080 218.22.246.34:1080 201.231.7.126:1080 200.168.132.162:1080 201.65.133.246:1080 218.56.32.2:1080 193.194.84.198:1080 201.21.154.191:1080 216.20.221.58:1080 201.245.51.138:1080 220.164.108.3:1080 200.179.218.47:1080 203.197.208.3:1080 213.93.75.149:1080 24.232.25.224:1080 200.126.145.178:1080 200.172.105.124:1080 209.254.227.243:1080 201.235.179.150:1080 200.114.70.101:1080 201.208.1.100:1080 201.249.11.91:1080 82.186.219.64:1080 81.22.87.134:1080 172.209.77.199:1080 200.204.176.83:1080 200.89.107.27:1080 61.12.47.144:1080 200.207.212.223:1080 201.252.65.103:1080 200.89.146.188:1080 210.212.176.238:1080 200.204.51.26:1080 200.114.174.159:1080 172.211.12.164:1080 58.51.89.8:1080 83.208.78.249:1080 200.179.246.102:1080 201.236.202.232:1080 200.45.47.217:1080 201.12.182.83:1080 | March 9, 2006, 6:46 AM |
| Beastfromteheast | Thank you hero. However, I still cannot connect. I now get this: [2:38:24 AM] All connections closed. [2:38:57 AM] [BNLS] Connecting... [2:38:57 AM] [BNLS] Connected! [2:38:57 AM] [BNLS] Authorized! [2:38:57 AM] [PROXY] Connecting... [2:38:58 AM] [PROXY] Connected! [2:38:58 AM] [PROXY] SOCKS5 login succeeded. (0) [2:38:58 AM] [BNET] Disconnected. [2:38:58 AM] All connections closed. | March 9, 2006, 7:39 AM |
| HeRo | they are socks4 | March 9, 2006, 7:59 AM |
| Yegg | [quote author=HeRo link=topic=14467.msg147997#msg147997 date=1141891180] they are socks4 [/quote] IIRC, specifying SOCKS4 as SOCKS5 will also work without a problem. | March 9, 2006, 2:16 PM |
| HeRo | that never worked for me (on a stealthbot, which he is using) | March 9, 2006, 6:38 PM |
| JoeTheOdd | If v5 of the SOCKS protocol supports reverse-compatiblity, it'd be the other way around. | March 10, 2006, 1:30 AM |