Reply to thread

Message

<blockquote data-quote="Mat Walker" data-source="post: 1239292" data-attributes="member: 148753">So this is driving me silly and soo regret 'up'grading to Win10 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />All has been working great.&nbsp; MP1 server on a W10 box and clients on a mix of W10 and W7 boxes,The Server installed a bunch of W10 updates and life became much harder.&nbsp; The file shares were the first I noticed had broken (outside MP); ended up having to reset IP/Winsock/etc on clients.Then found that none of my MP clients could connect to TV server anymore.&nbsp; Complaining of inability to connect to server or database.&nbsp; The server has no firewall (disabled) and the local TV client running on the server works fine.&nbsp; The client logs don't show any errors (which is fair enough, there is no error as far as they are concerned; they just cant connect) and the server doesn't register any connection coming in.&nbsp; I've tried using server name and ip address when connecting and I can remote desktop in (so 3389 is not blocked by anything); its odd.Has anyone else had this?&nbsp; Or is it just me? lolServer &amp; Clients at 1.15.0.0</blockquote>

[QUOTE="Mat Walker, post: 1239292, member: 148753"] So this is driving me silly and soo regret 'up'grading to Win10 :) All has been working great. MP1 server on a W10 box and clients on a mix of W10 and W7 boxes, The Server installed a bunch of W10 updates and life became much harder. The file shares were the first I noticed had broken (outside MP); ended up having to reset IP/Winsock/etc on clients. Then found that none of my MP clients could connect to TV server anymore. Complaining of inability to connect to server or database. The server has no firewall (disabled) and the local TV client running on the server works fine. The client logs don't show any errors (which is fair enough, there is no error as far as they are concerned; they just cant connect) and the server doesn't register any connection coming in. I've tried using server name and ip address when connecting and I can remote desktop in (so 3389 is not blocked by anything); its odd. Has anyone else had this? Or is it just me? lol Server & Clients at 1.15.0.0 [/QUOTE]

Verification