Page MenuHomeFeedback Tracker

"No message received" every 15 mins.
Closed, ResolvedPublic

Description

If I join ANY server after 15 mins I will get "no message received". If I try to exit as soon as I click yes the game becomes unresponsive for a minute or two. If I choose to wait it becomes it becomes responsive again and I can avoid having to end the task.

If I leave the server after 14 mins I can join again without any issues.

I have tried many things including:
-reinstall battleeye
-reinstall of dayz
-reinstall steam
-changed CPU and GPU back to stock clock settings
-disabled my sli fix (Force AFR2)
-ran steam from another location (separate drive to the OS)

and finally today I did a complete fresh install of Win 7 Pro 64 on my SSD...

None of this worked and I still get 'no message received' every 15 mins no matter what server I join.

The only other thing I can think that might (not) be worth trying is setting up a different Steam account and purchase another copy of the game.

The last time this happened was today the 19/8/2014 @ 6:38 pm (Australian CST). I was playing on:

DayZ AU 2-14 (Public/3PP:ON/Persistence:ON) 124737 - Hosted by

108.61.227.102

My Steam ID: http://steamcommunity.com/profiles/76561198012544623/home

My Tracert:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

I:\Users\new user>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]

               [-R] [-S srcaddr] [-4] [-6] target_name

Options:

    -d                 Do not resolve addresses to hostnames.
    -h maximum_hops    Maximum number of hops to search for target.
    -j host-list       Loose source route along host-list (IPv4-only).
    -w timeout         Wait timeout milliseconds for each reply.
    -R                 Trace round-trip path (IPv6-only).
    -S srcaddr         Source address to use (IPv6-only).
    -4                 Force using IPv4.
    -6                 Force using IPv6.

I:\Users\new user>tracert 108.61.227.102

Tracing route to 108.61.227.102.choopa.net [108.61.227.102]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  10.0.0.1
2     2 ms     1 ms     1 ms  home.gateway [192.168.1.254]
3    18 ms    17 ms    17 ms  lns20.adl6.on.ii.net [203.16.215.174]
4    18 ms    18 ms    17 ms  ae9.cr1.adl2.on.ii.net [150.101.225.20]
5    39 ms    38 ms    38 ms  ae1.cr1.mel4.on.ii.net [150.101.33.40]
6    39 ms    40 ms    38 ms  ae0.cr1.mel8.on.ii.net [150.101.33.11]
7    41 ms    40 ms    40 ms  ae3.br1.syd4.on.ii.net [150.101.33.26]
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.

10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I:\Users\new user>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]

               [-R] [-S srcaddr] [-4] [-6] target_name

Options:

    -d                 Do not resolve addresses to hostnames.
    -h maximum_hops    Maximum number of hops to search for target.
    -j host-list       Loose source route along host-list (IPv4-only).
    -w timeout         Wait timeout milliseconds for each reply.
    -R                 Trace round-trip path (IPv6-only).
    -S srcaddr         Source address to use (IPv6-only).
    -4                 Force using IPv4.
    -6                 Force using IPv6.

I:\Users\new user>tracert 108.61.227.102

Tracing route to 108.61.227.102.choopa.net [108.61.227.102]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  10.0.0.1
2     1 ms     1 ms     1 ms  home.gateway [192.168.1.254]
3    18 ms    16 ms    25 ms  lns20.adl6.on.ii.net [203.16.215.174]
4    25 ms    17 ms    18 ms  ae9.cr1.adl2.on.ii.net [150.101.225.20]
5    39 ms    38 ms    39 ms  ae1.cr1.mel4.on.ii.net [150.101.33.40]
6    51 ms    39 ms    38 ms  ae0.cr1.mel8.on.ii.net [150.101.33.11]
7    60 ms    38 ms    38 ms  ae3.br1.syd4.on.ii.net [150.101.33.26]
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.

10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I:\Users\new user>

I have included the relevant files in an .rar as mods have requested in the MANY other tickets created for this SAME issue.

Please let me know if you need anything else. I want to help you guys get this sorted.

Regards Troy.

Details

Legacy ID
742984168
Severity
None
Resolution
Not A Bug
Reproducibility
Always
Category
Server
Steps To Reproduce

Try to play on any server for 15 mins or more without disconnecting.

Event Timeline

chodeofwar set Category to Server.
chodeofwar set Reproducibility to Always.
chodeofwar set Severity to None.
chodeofwar set Resolution to Not A Bug.
chodeofwar set Legacy ID to 742984168.May 8 2016, 7:37 PM

Bump, I really hope this gets resolved during the Wednesday maintenance period.

OK some good news, I just played on experimental, the same version as stable and I did not lose connection once in over an hour.

I report back when the stable comes back online.

Issue resolved. Played on stable for a couple of hours no worries.

Kira added a comment.Aug 21 2014, 4:19 PM

Hey

Happy to hear that! Please do not hesitate to report any more bugs or crashes if found..

Thank You for your help!