Moon Guard disconnection issues compendium

Socksdeep-moon-guard · June 16, 2023, 1:23pm

I need to throw this out here. I posted a bit earlier about the same issue. Had uninstalled and reinstalled, no success. Right after I posted it occurred to me, the only thing I hadn’t done was manually log out of the launcher and back in. I did that and as soon as I logged in, i got the pop for the patch notes for the first time. I ran a scan and repair, it did do a very quick update. Logged back in and completed the entire quest I hadn’t been able to do for the past two weeks. There were no issues at all. I logged out and in on all 13 characters I have on MG, no black screen. This is the first time in two weeks. May want to try it if you haven’t.

Fropessor-proudmoore · June 16, 2023, 2:00pm

I can’t currently reproduce any disconnects and will continue to monitor. I’m now noticing MG game traffic going through the IP 137.221.96.152 from its previous of 137.221.97.120.

It does strike me as odd that you mention symptoms that haven’t been reported by anyone else - it’s possible that you were seeing the same issue as Disconnecting from the Server and unable to interact 100% with every feature of DragonFlight Expansion as all of those symptoms except for the chat issue are reported here.

I performed the same logout/login process as you, but several system restarts have been performed in the process for me, it’s followed me across multiple computers, and no data was downloaded upon restarting Battle.net for me.

Socksdeep-moon-guard · June 16, 2023, 2:15pm

You are correct, I didn’t see that other thread and it suits my issue better. I posted the reply over there. I just played for an hour with no issues, so that was definitely my problem, sorry it didn’t help you.

Wish you the best of luck!

Fropessor-proudmoore · June 16, 2023, 2:59pm

The input is still really appreciated, and hey - glad your issue is looking to be fixed as well. Thank you!

Fropessor-proudmoore · June 16, 2023, 3:16pm

All,

If you are experiencing the chronic disconnects on Moon Guard, and running a Windows OS, can you please do the following?

While logged onto a character, open Command Prompt.
Run the following command:

netstat -n | find " 137.221" | find “3724” | find “ESTABLISHED”

Output:

C:\Windows\System32>netstat -n | find " 137.221" | find “3724” | find “ESTABLISHED”
→ TCP 192.168.2.45:54017 137.221.96.152:3724 ESTABLISHED

Right-click that output, and click “Mark”. Highlight the output you received, then right-click again (Ctrl + C will also work).
Observe if any disconnects occur within that playing session, then paste the output into a reply. Attaching a WinMTR can help pinpoint the issue as well.

Edit: Added a leading space to only capture IPs beginning in 137.221. Unlikely, but you never know.

Edit 2: Change the test to a new methodology.

Edit 3: Condense instructions, improve netstat command.

Skelgarer-1963 · June 16, 2023, 4:04pm

Hey everyone,

Thank you all for taking the time to share your experiences and symptoms with these persistent disconnects. We really appreciate your efforts in isolating this and certainly want to find a permanent solution to the issue. There was an issue awhile back in which characters that are in guilds were experiencing this sort of disconnect behavior. Are these disconnects also affecting your guild-less characters?

Fropessor-proudmoore · June 16, 2023, 4:09pm

Heya Skelgarer,

Although I haven’t experienced disconnects today, the disconnects were previously experienced on (and primarily tested with) https://worldofwarcraft.blizzard.com/en-us/character/us/moon-guard/morimai, who is unfortunately both unguilded and hideously transmogged - a true double whammy.

Fropessor-proudmoore · June 16, 2023, 4:43pm

I reconnected just now, and this time, it connected to IP 137.221.97.120. Listed auctions, logged off of the character and once again disconnected. After reconnecting, it connected to 137.221.96.152. I then attempted to force a disconnect by logging out of that same character 20 times unsuccessfully.

I then exited the game and logged in again, which connected me to 137.221.97.120. I logged out of that character and once again logged out to a black character selection screen. pcap activity showed 6 retransmissions of an ACK (local → 137.221.97.120), followed by an RST/ACK 20 seconds later and a subsequent disconnection. Pressing “reconnect” connected me to 137.221.96.152, at which point I was no longer able to reproduce any disconnections.

Fropessor-proudmoore · June 16, 2023, 5:15pm

To further test this theory, I ran a test with the following method:

15 repetitions of:

Log out of, then log into the game.
Observe the server IP that is exchanging game traffic (port 3724).
Log out using the “Log out” button and observe. If not punted to a black screen → disconnection, log back into character, then use Logout button again (3 repetitions). If punted to a black screen, observe and then reconnect to game server.

Pastebin of results: https://pastebin.com/u0R0MaiL
pcap is available. Test was performed on this character: https://worldofwarcraft.blizzard.com/en-us/character/us/moon-guard/morimai, logged into Stormwind. All addons are disabled.

Would greatly appreciate if anyone on Moon Guard is willing to run a similar test!

Finraziell-wyrmrest-accord · June 16, 2023, 5:25pm

IP address lookup shows those addresses in Amsterdam/Holland Netherlands datacenter. Maybe there is an issue at that datacenter?

Nyxandria-moon-guard · June 16, 2023, 5:38pm

Most of my characters are guildless. Same problem.

Fropessor-proudmoore · June 16, 2023, 5:42pm

It was noted previously that the issue may be linked to the Greedy Emissary event. Although the event’s over, I ran a test in the most unpopulated area I could think of (sorry, Shrine of Seven Stars, it’s nothing personal). Results at: https://pastebin.com/rLRzALLR. Pcap is available, test was performed on a different unguilded character from the previous, with all addons disabled.

Centrism-wyrmrest-accord · June 16, 2023, 7:13pm

Same issues. Only on MG characters.

Hitaolin-aerie-peak · June 16, 2023, 7:56pm

(Also on Moon Guard)

Very interesting. For a small sample, I can repeat your results. If I connected to 137.221.96.152, I could log on, log off, switch characters several times without being disconnected. If I quit and reconnected until I got 137.221.97.120, I either experienced the disconnect within 10-15 seconds after logging in, or the black screen (no characters listed, only some of the decorations) disconnect.

Again, only a small sample size, but it did seem to agree with your results.

Nice find and hopefully this helps the troubleshooting!

Fropessor-proudmoore · June 16, 2023, 11:32pm

This is very good info - really appreciate the help and data here.

All,

Please provide info if possible, just like this. +1s help to recognize an issue, and data helps fix an issue. I feel confident in saying that I’ve identified where the issue that I’m running into is, and that my issue symptoms match those that have been commonly reported - but if this is truly a community issue, it’ll require a community effort.

You can check which address you are currently connected to by running this in Command Prompt:

netstat -n | find " 137.221" | find “3724” | find “ESTABLISHED”

Output:

C:\Windows\System32>netstat -n | find " 137.221" | find “3724” | find “ESTABLISHED”
TCP 192.168.2.45:54017 137.221.96.152:3724 ESTABLISHED

Please provide this info along with if you experience any disconnections (including if you don’t!) during a play session.

Evangeliøn-kelthuzad · June 17, 2023, 1:57pm

An update (for my soft disconnects): Yesterday played whole night without an issue, some decent 4, 5 hours, no random disconnects appeared. Two things were different, Diablo event is over and there was a bnet patch update (ver. 2.22.0). Will keep playing and see if the problem is resolved, will post future updates. Also following the Moon Guard thread to see if something eased since yesterday for you.

Fropessor-proudmoore · June 17, 2023, 4:11pm

That is really good news! Very glad to hear things are looking better on your end, and fingers crossed that it stays that way. The battle.net patch mention is interesting as well - Socksdeep also mentioned that their issue cleared up around the time of a battle.net patch being applied.

Since you’re not on Moon Guard, further points to a separate issue that was getting run into for you as well, as I’m still experiencing the same disconnects on MG as well as hearing of them from others.

Thanks for the update!

Xavara-moon-guard · June 17, 2023, 4:38pm

I am disconnecting 5-6 times within minutes upon the first start up of the game every single day for the past 2-3 weeks when playing on Moon Guard. Once I make it through those several disconnects, the game stabilizes and I can play with no problems for hours on end but once I close the WoW client and relaunch, it begins anew.

Nothing has changed on my end, other games play fine, it is just Moon Guard that seems to be causing this issue. I am not in a guild on Moon Guard either. No specific action or in game location seems to be causing this either. I could log in in Valdrakken, or I could log in in Thunder Bluff and the disconnect would happen all the same.

This is ONLY a Moon Guard problem. If I go to another server, like Wyrmrest Accord, I do not experience these DC’s when logging in at all but the moment I log out and attempt to log into Moon Guard, the DC’s begin to happen for several minutes until it finally lets me on to play.

Nyxandria-moon-guard · June 17, 2023, 5:18pm

I went from 7-8 disconnects last night to around 4-5. I’ve noticed it happens more for me anywhere in the Eastern Kingdoms (but still happens everywhere.)

Supertarget-moon-guard · June 17, 2023, 5:36pm

Moon Guard player. I ran

netstat 3 -n | find " 137." | find “3724”

while playing just to monitor stuff. Here is me playing

Starting the netstat while playing the game and connected

TCP 10.0.0.42:56657 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 ESTABLISHED

Exiting the game to try and replicate DC

TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT

Reconnecting to the game

TCP 10.0.0.42:57045 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57046 137.221.97.120:3724 ESTABLISHED

Booted back to RECONNECT button on main screen

TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:56657 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT

Logged back in, continued to play without getting disconnected well beyond me posting this

TCP 10.0.0.42:57140 137.221.97.120:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57045 137.221.96.152:3724 TIME_WAIT
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57140 137.221.97.120:3724 TIME_WAIT
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED
TCP 10.0.0.42:57141 137.221.96.152:3724 ESTABLISHED

Seems to be related to the .120 connection but there was a point I reconnected to a .120 and did not disconnect. But with that said, I have never seen myself disconnecting from a .152. Will continue to run this and pay attention.