Would you mind of closing connection of 127.0.0.1?

Dear.Blizzard

Thanks to play diablo2 resurrected,always.

The netstat results are *1 and *2 and *3 on playing diablo2 resurrected.
Do you think my network have weakness of sneak?

Especially, would you mind of closing connection-sessions of 127.0.0.1 ?
For example *1 and *3.

Because my network connection was disturbance after closing connection-sessions of 127.0.0.1.
There are network-disturbance for example movies in *4, but the internet radio was on.

It seems to take effort to comfirm, but i will escape from sneak.

Best regards
------------------------ *1 --------------------------
[D2R.exe]
UDP 127.0.0.1:1900 :
SSDPSRV
------------------------ *2 -------------------------
[Battle.net.exe]
TCP 192.168.2.102:55752 137.221.105.152:1119 ESTABLISHED
[D2R.exe]
TCP 192.168.2.102:55755 137.221.106.188:https ESTABLISHED
[D2R.exe]
TCP 192.168.2.102:55966 va:https ESTABLISHED
------------------------- *3 ------------------------
[Agent.exe]
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56261 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56262 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56263 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56264 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56266 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56268 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56269 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56270 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56271 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56272 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56273 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56274 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56275 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56277 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56278 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56279 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56280 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56283 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56284 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56286 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56289 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56290 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56291 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56292 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56296 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56299 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56300 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56301 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56302 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56305 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56306 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56307 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56308 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56309 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56310 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56311 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56312 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56313 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56314 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56315 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56317 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56318 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56320 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56321 TIME_WAIT
TCP 127.0.0.1:1120 DESKTOP-398VK2U:56322 TIME_WAIT
TCP 127.0.0.1:22885 DESKTOP-398VK2U:0 LISTENING
[Battle.net.exe]
TCP 127.0.0.1:44338 DESKTOP-398VK2U:55725 ESTABLISHED
[D2R.exe]
TCP 127.0.0.1:55495 DESKTOP-398VK2U:55496 ESTABLISHED
[Battle.net.exe]
TCP 127.0.0.1:55496 DESKTOP-398VK2U:55495 ESTABLISHED
[Battle.net.exe]
TCP 127.0.0.1:55720 DESKTOP-398VK2U:55721 ESTABLISHED
[D2R.exe]
TCP 127.0.0.1:55721 DESKTOP-398VK2U:55720 ESTABLISHED
[D2R.exe]
TCP 127.0.0.1:55725 DESKTOP-398VK2U:44338 ESTABLISHED
[D2R.exe]
TCP 127.0.0.1:56265 DESKTOP-398VK2U:1120 TIME_WAIT
TCP 127.0.0.1:56280 DESKTOP-398VK2U:1120 TIME_WAIT
TCP 127.0.0.1:56298 DESKTOP-398VK2U:1120 TIME_WAIT
TCP 127.0.0.1:56316 DESKTOP-398VK2U:1120 TIME_WAIT
TCP 192.168.2.102:139 DESKTOP-398VK2U:0 LISTENING
------------------------- *4 ------------------------
2023/4/16 Diablo2 resurrected was Interrupted when the timer was run out, but the radio was on.

2023/04/13, on playing Diablo2 resurrected, transmission speed was under 0.1KB/s, so the game connection has been interrupted.

2023/03/21, The network disturbance was happened when Life about 600 on fighting Diablo clone .
Ladder softcore, ASIA-server

2023/03/17, The network disturbance was happened, attached data-transmission-speed which was a minimum.

2023/03/17, The Lv93-Sorceress have died from stoppage connection at US-server.

2023/03/15, the laggy connection was more rapidly.

2023/03/13 the connection was interrupted at 9:06-9:08 on the Baal-throne.

this lag phenomenon was occurred at ASIA-server ,2023/03/07 ,PM 23:00 JPN.

,2023/03/08,the same phenomenon was occurred, so I captured and uploaded.

2023/03/13,The stoppage phenomenon

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.