I have been having some strange issues with NWN of late - which seem related to whenever I am connected to my network. When I am, NWN will periodically go non-responsive (music and sound still plays, but the game screen and gamplay itself will freeze). This happens often during play - and is guaranteed to do so at least once when loading the initial "splash screen" that appears straight after the intro videos. Sometimes it recovers in 10 or so seconds, sometimes not.
NWN provides no logs of this - the only contents of "nwclientLog1.txt" being "nwsync: reconfigured successfully".
On closer inspection, it seems if I disable my Ethernet connection, it works perfectly. This lead me to taking a peek at what was happening with a processmon. Results of which are that NWN seems to continuously try connecting to "Jim-Chillblast" (the hostname of the PC I run the game on), with different ports. These take a few seconds each time and it continuously loops around this with apparently no end in sight. This APPEARS to be the thing that's creating these freeze and crashes, but I have no idea what to do (if anything) to fix it.
I have tried disabling IPv6 to no avail and there is nothing out of the ordinary with my connection - other than my router not supporting NAT Loopback. Given the request is a local one, pointing to a local resource (the originating computer), I doubt this has anything to do with it - but thought it worth mentioning as you never know.
DXDiag reports no issues with graphics or sound drivers... and literally everything else works fine. I have tried all the obvious stuff such as uninstalling, verifying files, compatibility mode, removing mods, deleting the settings folder in Documents etc. At a loss as to how to fix it at present - if there is indeed anything I can do. It makes the game completely unplayable though.
You can see in the attached screenshots how long the TCP requests take (and there are a lot of them - all to the same place). So what's going on here? Why does this happen when connected to the internet/LAN, but not otherwise - and what on earth can be done to fix it?