Перейти к содержанию

НЕ ботает контактовский джабер через прокси


Рекомендуемые сообщения

Собственно такая проблема настроил в qip учетную запись от контакта все бы хорошо но не в какую не хочет работать чрез прокси сервер, без прокси конектится без проблем.

Раскрывающийся текст:

17:06:48,406|00dc| OnQipMessage: msg = 47, wParam = 1247, lParam = 920, Result = 0

17:06:51,281|00dc| ~OnQipMessage: msg = 47, wParam = 1247, lParam = 920, Result = 0

17:06:51,281|00dc| updateCurStatus (255)
17:06:51,281|00dc| postProtoMessage/a1
17:06:51,281|00dc| handleQipMessage: 48
17:06:51,281|00dc| postProtoMessage/a2
17:06:51,281|1568| Thread started: type=0,step=1
17:06:51,296|13a4| DNS: failed to resolve
17:06:51,296|1568| _xmpp-client._tcp. not resolved - 183
17:06:51,296|1568| Thread type=0 server='vk.com' port='5222'
17:06:51,296|1568| WsConnect: proxified - 5, 192.168.1.10:1070
17:07:12,203|1568| WsConnect_SOCKS5: wrong response #2|
00000000 05 01 00 01 00								  | .....		   
17:07:12,203|1568| Connection failed ( 0 )
17:07:12,203|1568| Thread ended
17:07:12,203|1568| Exiting: going to offline
17:07:12,203|1568| updateCurStatus (13)
17:07:12,203|1568| postProtoMessage(s1): #48, 13, 100009, 0
17:07:12,203|1568| postProtoMessage(s2): #48, 13, 100009, 0
17:07:12,203|00dc| handleAsyncQipMessage: 48
17:07:12,203|1568| Exiting: offlining
17:07:12,203|00dc| handleQipMessage: 48
17:07:12,203|1568| Exiting: offlining-done
17:07:12,203|1568| postProtoMessage(s1): #26, 4, 100009, 0
17:07:12,203|1568| postProtoMessage(s2): #26, 4, 100009, 0
17:07:12,203|1568| Exiting: #3
17:07:12,203|1568| Protocol will be reconnected in 3 s.
17:07:12,203|1568| Exiting: #4
17:07:12,203|1568| Exiting: #5
17:07:12,203|1568| Exiting: #6
17:07:12,203|1568| Exiting: #6a
17:07:12,203|1568| Exiting: #6b
17:07:12,203|1568| Exiting: #6c
17:07:12,203|1568| Exiting: #6d
17:07:12,203|1568| Exiting: #7
17:07:12,218|00dc| handleAsyncQipMessage: 26
17:07:12,218|00dc| handleQipMessage: 26
17:07:15,203|00dc| Execution of scheduled reconnection
17:07:15,203|00dc| updateCurStatus (255)
17:07:15,203|00dc| postProtoMessage/a1
17:07:15,203|00dc| handleQipMessage: 48
17:07:15,218|00dc| postProtoMessage/a2
17:07:15,218|1718| Thread started: type=0,step=1
17:07:15,218|04bc| DNS: failed to resolve
17:07:15,218|1718| _xmpp-client._tcp. not resolved - 183
17:07:15,218|1718| Thread type=0 server='vk.com' port='5222'
17:07:15,218|1718| WsConnect: proxified - 5, 192.168.1.10:1070
17:07:36,078|1718| WsConnect_SOCKS5: wrong response #2|
00000000 05 01 00 01 00								  | .....		   
17:07:36,078|1718| Connection failed ( 0 )
17:07:36,078|1718| Thread ended
17:07:36,078|1718| Exiting: going to offline
17:07:36,078|1718| updateCurStatus (13)
17:07:36,078|1718| postProtoMessage(s1): #48, 13, 100009, 0
17:07:36,078|1718| postProtoMessage(s2): #48, 13, 100009, 0
17:07:36,078|00dc| handleAsyncQipMessage: 48
17:07:36,078|1718| Exiting: offlining
17:07:36,078|00dc| handleQipMessage: 48
17:07:36,078|1718| Exiting: offlining-done
17:07:36,078|1718| postProtoMessage(s1): #26, 6, 100009, 0
17:07:36,078|1718| postProtoMessage(s2): #26, 6, 100009, 0
17:07:36,078|1718| Exiting: #3
17:07:36,078|1718| Protocol will be reconnected in 7 s.
17:07:36,078|1718| Exiting: #4
17:07:36,078|1718| Exiting: #5
17:07:36,078|1718| Exiting: #6
17:07:36,078|1718| Exiting: #6a
17:07:36,078|1718| Exiting: #6b
17:07:36,078|1718| Exiting: #6c
17:07:36,078|1718| Exiting: #6d
17:07:36,078|1718| Exiting: #7
17:07:36,093|00dc| handleAsyncQipMessage: 26
17:07:36,093|00dc| handleQipMessage: 26
17:07:43,078|00dc| Execution of scheduled reconnection
17:07:43,078|00dc| updateCurStatus (255)
17:07:43,078|00dc| postProtoMessage/a1
17:07:43,078|00dc| handleQipMessage: 48
17:07:43,093|00dc| postProtoMessage/a2
17:07:43,093|14ac| Thread started: type=0,step=1
17:07:43,093|0d58| DNS: failed to resolve
17:07:43,093|14ac| _xmpp-client._tcp. not resolved - 183
17:07:43,093|14ac| Thread type=0 server='vk.com' port='5222'
17:07:43,093|14ac| WsConnect: proxified - 5, 192.168.1.10:1070
17:08:04,062|14ac| WsConnect_SOCKS5: wrong response #2|
00000000 05 01 00 01 00								  | .....		   
17:08:04,062|14ac| Connection failed ( 0 )
17:08:04,062|14ac| Thread ended
17:08:04,062|14ac| Exiting: going to offline
17:08:04,062|14ac| updateCurStatus (13)
17:08:04,062|14ac| postProtoMessage(s1): #48, 13, 100009, 0
17:08:04,062|14ac| postProtoMessage(s2): #48, 13, 100009, 0
17:08:04,062|00dc| handleAsyncQipMessage: 48
17:08:04,062|14ac| Exiting: offlining
17:08:04,062|00dc| handleQipMessage: 48
17:08:04,062|14ac| Exiting: offlining-done
17:08:04,062|14ac| postProtoMessage(s1): #26, 6, 100009, 0
17:08:04,062|14ac| postProtoMessage(s2): #26, 6, 100009, 0
17:08:04,062|14ac| Exiting: #3
17:08:04,062|14ac| Protocol will be reconnected in 20 s.
17:08:04,062|14ac| Exiting: #4
17:08:04,062|14ac| Exiting: #5
17:08:04,062|14ac| Exiting: #6
17:08:04,062|14ac| Exiting: #6a
17:08:04,062|14ac| Exiting: #6b
17:08:04,062|14ac| Exiting: #6c
17:08:04,062|14ac| Exiting: #6d
17:08:04,062|14ac| Exiting: #7
17:08:04,078|00dc| handleAsyncQipMessage: 26
17:08:04,078|00dc| handleQipMessage: 26
17:08:24,062|00dc| Execution of scheduled reconnection
17:08:24,062|00dc| updateCurStatus (255)
17:08:24,062|00dc| postProtoMessage/a1
17:08:24,062|00dc| handleQipMessage: 48
17:08:24,062|00dc| postProtoMessage/a2
17:08:24,062|102c| Thread started: type=0,step=1
17:08:24,093|0e60| DNS: failed to resolve
17:08:24,093|102c| _xmpp-client._tcp. not resolved - 183
17:08:24,093|102c| Thread type=0 server='vk.com' port='5222'
17:08:24,093|102c| WsConnect: proxified - 5, 192.168.1.10:1070
17:08:45,046|102c| WsConnect_SOCKS5: wrong response #2|
00000000 05 01 00 01 00								  | .....		   
17:08:45,046|102c| Connection failed ( 0 )
17:08:45,046|102c| Thread ended
17:08:45,046|102c| Exiting: going to offline
17:08:45,046|102c| updateCurStatus (13)
17:08:45,046|102c| postProtoMessage(s1): #48, 13, 100009, 0
17:08:45,046|102c| postProtoMessage(s2): #48, 13, 100009, 0
17:08:45,046|102c| Exiting: offlining
17:08:45,046|102c| Exiting: offlining-done
17:08:45,046|102c| postProtoMessage(s1): #26, 6, 100009, 0
17:08:45,046|102c| postProtoMessage(s2): #26, 6, 100009, 0
17:08:45,046|102c| Exiting: #3
17:08:45,046|102c| Protocol will be reconnected in 55 s.
17:08:45,046|102c| Exiting: #4
17:08:45,046|102c| Exiting: #5
17:08:45,046|102c| Exiting: #6
17:08:45,046|102c| Exiting: #6a
17:08:45,046|102c| Exiting: #6b
17:08:45,046|102c| Exiting: #6c
17:08:45,046|102c| Exiting: #6d
17:08:45,046|102c| Exiting: #7
17:08:45,062|00dc| handleAsyncQipMessage: 48
17:08:45,062|00dc| handleQipMessage: 48
17:08:45,109|00dc| handleAsyncQipMessage: 26
17:08:45,109|00dc| handleQipMessage: 26
17:09:40,046|00dc| Execution of scheduled reconnection
17:09:40,046|00dc| updateCurStatus (255)
17:09:40,046|00dc| postProtoMessage/a1
17:09:40,046|00dc| handleQipMessage: 48
17:09:40,046|00dc| postProtoMessage/a2
17:09:40,046|151c| Thread started: type=0,step=1
17:09:40,078|1684| DNS: failed to resolve
17:09:40,078|151c| _xmpp-client._tcp. not resolved - 183
17:09:40,078|151c| Thread type=0 server='vk.com' port='5222'
17:09:40,078|151c| WsConnect: proxified - 5, 192.168.1.10:1070
17:10:01,078|151c| WsConnect_SOCKS5: wrong response #2|
00000000 05 01 00 01 00								  | .....		   
17:10:01,078|151c| Connection failed ( 0 )
17:10:01,078|151c| Thread ended
17:10:01,078|151c| Exiting: going to offline
17:10:01,078|151c| updateCurStatus (13)
17:10:01,078|151c| postProtoMessage(s1): #48, 13, 100009, 0
17:10:01,078|151c| postProtoMessage(s2): #48, 13, 100009, 0
17:10:01,078|00dc| handleAsyncQipMessage: 48
17:10:01,078|151c| Exiting: offlining
17:10:01,078|00dc| handleQipMessage: 48
17:10:01,078|151c| Exiting: offlining-done
17:10:01,078|151c| postProtoMessage(s1): #26, 6, 100009, 0
17:10:01,078|151c| postProtoMessage(s2): #26, 6, 100009, 0
17:10:01,078|151c| Exiting: #3
17:10:01,078|151c| Protocol will be reconnected in 150 s.
17:10:01,078|151c| Exiting: #4
17:10:01,078|151c| Exiting: #5
17:10:01,078|151c| Exiting: #6
17:10:01,078|151c| Exiting: #6a
17:10:01,078|151c| Exiting: #6b
17:10:01,078|151c| Exiting: #6c
17:10:01,078|151c| Exiting: #6d
17:10:01,078|151c| Exiting: #7
17:10:01,109|00dc| handleAsyncQipMessage: 26
17:10:01,109|00dc| handleQipMessage: 26

 

Изменено пользователем Mark D. Pearlstone
Скрыл код под спойлер
Ссылка на комментарий
Поделиться на другие сайты

У вас не получится подключиться через прокси ни к чему! Я в школе так же мучаюсь, хоть у нас там стоит Linux, в интернет ходим через proxy, а в mail.ru агент, вконтакте через клиент, в jabber, ISQ не подключишься. Такой вот он вредный прокси сервер. Прокси сервер блокирует подобные попытки подключения! Я даже настраивал в самой программе подключение к интернету, указывал порт, шлюзы, но всё это пустой номер.

Ссылка на комментарий
Поделиться на другие сайты

Пожалуйста, войдите, чтобы комментировать

Вы сможете оставить комментарий после входа в



Войти
×
×
  • Создать...