[Problème] Connexion au serveur

janvier 2015 modifié dans Support technique
Bonsoir

J'ai un problème qui arrive régulièrement quand je suis connectés à Frozenway sur mon PC portable mais qui n'est pas présent quand je suis connectés sur mon PC fixe.

je suis connectés à WoW et après le reset des 2h , il m'arrive de plus pouvoir me connecter au jeu et cela peut durer 10min comme 2 jours alors que je suis bien connectés sur les serveurs. La navigation est possible mais pas moyen de m'identifier sur le jeu. Pouvez-vous m'éclairer sur le sujet ? Merci d'avance

PS : Je précise que je n'ai pas Avast ou autres Anti-Virus/Logiciel qui bloque ma connexion et que je met bien 3 fois plus de temps à me connecter au serveur sur le PC portable que sur celui fixe. Pour ce qui est des autres protocoles Https et Http j'ai jamais réussis a les faire fonctionner alors que je suis bien connecter dessus :)

Je suis connectés à SFR WiFi Public et j'ai suivis à la lettre votre aide à l'utilisation suivante :
http://www.frozenway.com/forum/index.php?p=/discussion/139/reconnexion-automatique-sfr-wifi#Item_1

Voici mon Journal :

Bonne Lecture x)

FrozenWay version 1.6.5
----------------------------------
Server: public-02-fr-04
Protocol: OpenVPN
----------------------------------
Sun Jan 04 02:25:59 2015 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013

Sun Jan 04 02:26:00 2015 Control Channel Authentication: using 'C:/Program Files/FrozenWay 1.6.5/etc/keys/auth.key' as a OpenVPN static key file
Sun Jan 04 02:26:00 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 04 02:26:00 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 04 02:26:00 2015 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sun Jan 04 02:26:00 2015 Attempting to establish TCP connection with [AF_INET]176.31.6.211:443
Sun Jan 04 02:26:00 2015 TCP connection established with [AF_INET]176.31.6.211:443
Sun Jan 04 02:26:00 2015 TCPv4_CLIENT link local: [undef]
Sun Jan 04 02:26:00 2015 TCPv4_CLIENT link remote: [AF_INET]176.31.6.211:443

Sun Jan 04 02:26:00 2015 TLS: Initial packet from [AF_INET]176.31.6.211:443, sid=7903cb87 69d6c8da

Sun Jan 04 02:26:01 2015 VERIFY OK: depth=1, C=FR, ST=France, L=Paris, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com
Sun Jan 04 02:26:01 2015 VERIFY OK: nsCertType=SERVER
Sun Jan 04 02:26:01 2015 VERIFY OK: depth=0, C=FR, ST=France, O=FrozenWay, OU=FrozenWay, CN=FrozenWay, emailAddress=admin@frozenway.com

Sun Jan 04 02:26:01 2015 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 04 02:26:01 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 04 02:26:01 2015 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 04 02:26:01 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 04 02:26:01 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Jan 04 02:26:01 2015 [FrozenWay] Peer Connection Initiated with [AF_INET]176.31.6.211:443

Sun Jan 04 02:26:03 2015 SENT CONTROL [FrozenWay]: 'PUSH_REQUEST' (status=1)
Sun Jan 04 02:26:03 2015 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.4.0.1,dhcp-option WINS 10.4.0.1,route 10.4.0.1,topology net30,socket-flags TCP_NODELAY,ifconfig 10.4.0.6 10.4.0.5'
Sun Jan 04 02:26:03 2015 OPTIONS IMPORT: --socket-flags option modified
Sun Jan 04 02:26:03 2015 OPTIONS IMPORT: --ifconfig/up options modified
Sun Jan 04 02:26:03 2015 OPTIONS IMPORT: route options modified
Sun Jan 04 02:26:03 2015 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

Sun Jan 04 02:26:03 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Jan 04 02:26:03 2015 open_tun, tt->ipv6=0
Sun Jan 04 02:26:03 2015 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{565D88CA-3E83-4A86-92BE-CFBE631BA89C}.tap
Sun Jan 04 02:26:03 2015 TAP-Windows Driver Version 9.9
Sun Jan 04 02:26:03 2015 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.0.6/255.255.255.252 on interface {565D88CA-3E83-4A86-92BE-CFBE631BA89C} [DHCP-serv: 10.4.0.5, lease-time: 31536000]
Sun Jan 04 02:26:03 2015 Successful ARP Flush on interface [31] {565D88CA-3E83-4A86-92BE-CFBE631BA89C}

Sun Jan 04 02:26:08 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:08 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:13 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:13 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:14 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:14 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:15 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:15 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:17 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:17 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:18 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:18 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:19 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:19 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:21 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:21 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:22 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:22 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:23 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:23 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:24 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:24 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:25 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:25 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:26 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:26 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:27 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:27 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:28 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:28 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:29 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:29 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:30 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:30 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:31 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:31 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:32 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:32 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:33 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:33 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:34 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:34 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:35 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:35 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:36 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:36 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:37 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:37 2015 Route: Waiting for TUN/TAP interface to come up...

Waking up the interface...
Sun Jan 04 02:26:38 2015 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jan 04 02:26:38 2015 C:\Windows\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.0.5
Sun Jan 04 02:26:38 2015 Warning: route gateway is not reachable on any active network adapters: 10.4.0.5
Sun Jan 04 02:26:38 2015 Route addition via IPAPI failed [adaptive]
Sun Jan 04 02:26:38 2015 Route addition fallback to route.exe
Sun Jan 04 02:26:38 2015 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.2.1 p=0 i=11 t=4 pr=3 a=4059 h=0 m=25/0/0/0/0
10.4.0.1 255.255.255.255 10.4.0.5 p=0 i=11 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.7.0.4 255.255.255.252 10.7.0.6 p=0 i=31 t=3 pr=3 a=3556 h=0 m=286/0/0/0/0
10.7.0.6 255.255.255.255 10.7.0.6 p=0 i=31 t=3 pr=3 a=3556 h=0 m=286/0/0/0/0
10.7.0.7 255.255.255.255 10.7.0.6 p=0 i=31 t=3 pr=3 a=3556 h=0 m=286/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=4104 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=4104 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=4104 h=0 m=306/0/0/0/0
169.254.0.0 255.255.0.0 169.254.123.234 p=0 i=37 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
169.254.0.0 255.255.0.0 169.254.123.250 p=0 i=36 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
169.254.123.234 255.255.255.255 169.254.123.234 p=0 i=37 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
169.254.123.250 255.255.255.255 169.254.123.250 p=0 i=36 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.123.234 p=0 i=37 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.123.250 p=0 i=36 t=3 pr=3 a=4080 h=0 m=286/0/0/0/0
192.168.2.0 255.255.255.0 192.168.2.70 p=0 i=11 t=3 pr=3 a=4059 h=0 m=281/0/0/0/0
192.168.2.70 255.255.255.255 192.168.2.70 p=0 i=11 t=3 pr=3 a=4059 h=0 m=281/0/0/0/0
192.168.2.255 255.255.255.255 192.168.2.70 p=0 i=11 t=3 pr=3 a=4059 h=0 m=281/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=4104 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 10.7.0.6 p=0 i=31 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 169.254.123.250 p=0 i=36 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 169.254.123.234 p=0 i=37 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 192.168.2.70 p=0 i=11 t=3 pr=3 a=4065 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=4104 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 10.7.0.6 p=0 i=31 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 169.254.123.250 p=0 i=36 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 169.254.123.234 p=0 i=37 t=3 pr=3 a=4083 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 192.168.2.70 p=0 i=11 t=3 pr=3 a=4065 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9 #2
Index = 37
GUID = {7ADA4662-1E22-4B7F-8530-6CA87BCD5264}
IP = 169.254.123.234/255.255.0.0
MAC = 00:ff:7a:da:46:62
GATEWAY = 0.0.0.0/255.255.255.255
DNS SERV =
TAP-Windows Adapter V9
Index = 36
GUID = {F1496BF9-BA78-4694-9281-68758B8D264D}
IP = 169.254.123.250/255.255.0.0
MAC = 00:ff:f1:49:6b:f9
GATEWAY = 0.0.0.0/255.255.255.255

DNS SERV =
TAP-Windows Adapter V9
Index = 31
GUID = {565D88CA-3E83-4A86-92BE-CFBE631BA89C}
IP = 10.7.0.6/255.255.255.252
MAC = 00:ff:56:5d:88:ca
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 10.7.0.5/255.255.255.255
DHCP LEASE OBTAINED = Sun Jan 04 01:27:21 2015
DHCP LEASE EXPIRES = Mon Jan 04 01:27:21 2016

DNS SERV = 10.7.0.1/255.255.255.255
Microsoft Virtual WiFi Miniport Adapter
Index = 13
GUID = {E7070230-6CEA-434A-8880-6442441DF55D}
IP = 0.0.0.0/0.0.0.0
MAC = 92:9f:fa:0f:87:96
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sun Jan 04 02:26:39 2015
DHCP LEASE EXPIRES = Sun Jan 04 02:26:39 2015

DNS SERV =
Atheros AR5B95 Wireless Network Adapter
Index = 11
GUID = {3F7BAEE0-2D19-4ADD-A830-2F383C64605B}
IP = 192.168.2.70/255.255.255.0
MAC = 88:9f:fa:0f:87:96
GATEWAY = 192.168.2.1/255.255.255.255
DHCP SERV = 192.168.2.1/255.255.255.255
DHCP LEASE OBTAINED = Sun Jan 04 02:19:00 2015
DHCP LEASE EXPIRES = Sun Jan 04 02:39:00 2015

DNS SERV = 109.0.66.10/255.255.255.255 109.0.66.20/255.255.255.255
Atheros AR8152 PCI-E Fast Ethernet Controller (NDIS 6.20)
Index = 10
GUID = {1B34C40E-4AEB-48D6-982F-CF055C8727B6}
IP = 0.0.0.0/0.0.0.0
MAC = 1c:75:08:39:ce:8d
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Sun Jan 04 02:26:39 2015
DHCP LEASE EXPIRES = Sun Jan 04 02:26:39 2015

DNS SERV =
Sun Jan 04 02:26:39 2015 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

IPv4 routing table :
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.70 25
0.0.0.0 128.0.0.0 10.4.0.5 10.7.0.6 30
2.21.136.13 255.255.255.255 192.168.2.1 192.168.2.70 25
10.4.0.1 255.255.255.255 10.4.0.5 192.168.2.70 26
10.7.0.4 255.255.255.252 10.7.0.6 10.7.0.6 286
10.7.0.6 255.255.255.255 10.7.0.6 10.7.0.6 286
10.7.0.7 255.255.255.255 10.7.0.6 10.7.0.6 286
62.122.9.80 255.255.255.255 192.168.2.1 192.168.2.70 25
109.0.66.10 255.255.255.255 192.168.2.1 192.168.2.70 25
109.0.66.20 255.255.255.255 192.168.2.1 192.168.2.70 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
128.0.0.0 128.0.0.0 10.4.0.5 10.7.0.6 30
169.254.0.0 255.255.0.0 169.254.123.234 169.254.123.234 286
169.254.0.0 255.255.0.0 169.254.123.250 169.254.123.250 286
169.254.123.234 255.255.255.255 169.254.123.234 169.254.123.234 286
169.254.123.250 255.255.255.255 169.254.123.250 169.254.123.250 286
169.254.255.255 255.255.255.255 169.254.123.234 169.254.123.234 286
169.254.255.255 255.255.255.255 169.254.123.250 169.254.123.250 286
173.194.67.99 255.255.255.255 192.168.2.1 192.168.2.70 25
173.194.67.103 255.255.255.255 192.168.2.1 192.168.2.70 25
173.194.67.104 255.255.255.255 192.168.2.1 192.168.2.70 25
173.194.67.105 255.255.255.255 192.168.2.1 192.168.2.70 25
173.194.67.106 255.255.255.255 192.168.2.1 192.168.2.70 25
173.194.67.147 255.255.255.255 192.168.2.1 192.168.2.70 25
176.31.6.211 255.255.255.255 192.168.2.1 192.168.2.70 25
178.251.204.166 255.255.255.255 192.168.2.1 192.168.2.70 25
192.168.2.0 255.255.255.0 192.168.2.70 192.168.2.70 281
192.168.2.70 255.255.255.255 192.168.2.70 192.168.2.70 281
192.168.2.255 255.255.255.255 192.168.2.70 192.168.2.70 281
204.79.197.200 255.255.255.255 192.168.2.1 192.168.2.70 25
213.186.33.87 255.255.255.255 192.168.2.1 192.168.2.70 25
217.109.56.160 255.255.255.255 192.168.2.1 192.168.2.70 25
224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
224.0.0.0 240.0.0.0 10.7.0.6 10.7.0.6 286
224.0.0.0 240.0.0.0 169.254.123.250 169.254.123.250 286
224.0.0.0 240.0.0.0 169.254.123.234 169.254.123.234 286
224.0.0.0 240.0.0.0 192.168.2.70 192.168.2.70 281
255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
255.255.255.255 255.255.255.255 10.7.0.6 10.7.0.6 286
255.255.255.255 255.255.255.255 169.254.123.250 169.254.123.250 286
255.255.255.255 255.255.255.255 169.254.123.234 169.254.123.234 286
255.255.255.255 255.255.255.255 192.168.2.70 192.168.2.70 281

Réponses

  • Le problème persiste toujours, impossible de me connectés depuis une dizaine d'heure sur WoW et autres jeux en ligne.
  • Salut,

    Et si tu redémarres ton PC portable ?
  • janvier 2015 modifié
    Je l'ai déjà fait mais ça remarche une fois sur 5. Je me demande si c'est pas du à la puissance de mon PC qui est tellement peu performant que les infos au serveur passe mal et que cela empêche la connexion.
  • C'est un problème d'obtention de l'adresse IP par DHCP. Tu peux essayer de changer la méthode d'obtention de l'adresse IP dans les options réseau de FrozenWay.
  • D'accord, Je vous tiens au courant si cela ne fonctionne pas. Merci
Connectez-vous ou Inscrivez-vous pour répondre.