Random association aborts with Windows Server over network

Association gets aborted with Pynetdicom on windows server when tried from network. Let me describe what happens:

On my windows server:

> python -m pynetdicom storescp 5253 -v --ignore
I: Accepting Association
I: Association Aborted (A-P-ABORT)

IP of my server is 192.168.0.119. What I did on my client over wifi.

$ echoscu -v 192.168.0.119 5253
I: Requesting Association
I: Association Accepted (Max Send PDV: 16370)
I: Sending Echo Request (MsgID 1)
E: Echo Failed: 0006:0317 Peer aborted Association (or never connected)
I: Peer Aborted Association

I have tried to reproduce the same thing with dcmtk’s storescp and there was no issue. Also run pynetdicom inside a ubunut docker on windows and there was no issue either.

Surprisingly if I use pynetdicom’s echoscu client, it works

$ python -m pynetdicom echoscu -v 192.168.0.119 5253
I: Requesting Association
I: Association Accepted
I: Sending Echo Request: MsgID 1
I: Received Echo Response (Status: Success)
I: Releasing Association

If I did echoscu from the windows server, it works!

.\bin\echoscu.exe -v localhost 5253
I: Requesting Association
I: Association Accepted (Max Send PDV: 16370)
I: Sending Echo Request (MsgID 1)
I: Received Echo Response (Success)
I: Releasing Association

[scaramallion]

And change to self.ae = ae = AE() so it get’s cleaned up properly if it fails.

[scaramallion]

test_transport.py::TestAssociationServer

You’ll have to add a_associate_rq to the imports from .encoded_pdu_items as well