Normal
I think I'm going to have to do a server rebuild. I was on it all last night. Tried uninstalling network 'card', re-installing, turning firewall on then off again, finding every 'tweak' I could and fiddling (admittedly relatively blindly - I'm techy, but there some stuff in W10 I find baffling lol) with it but no; MP clients just 'cant see' the server.I can open file shares, access Remote Desktop and browse to a website being hosted on the server - but all the MP clients are quite adamant; they cannot connect to server or database. Local client running on the server is ok so thye TV server and database are running all ok.Using TCPView from Sysinternals, I can see TVService is listening on 554 & 31456 and MySQL on 3306 - and also that the local client is hooked in to them. So why are the clients saying they cannot connect to the TV service or the database?Is it really only me this has happened to?
I think I'm going to have to do a server rebuild. I was on it all last night. Tried uninstalling network 'card', re-installing, turning firewall on then off again, finding every 'tweak' I could and fiddling (admittedly relatively blindly - I'm techy, but there some stuff in W10 I find baffling lol) with it but no; MP clients just 'cant see' the server.
I can open file shares, access Remote Desktop and browse to a website being hosted on the server - but all the MP clients are quite adamant; they cannot connect to server or database. Local client running on the server is ok so thye TV server and database are running all ok.
Using TCPView from Sysinternals, I can see TVService is listening on 554 & 31456 and MySQL on 3306 - and also that the local client is hooked in to them. So why are the clients saying they cannot connect to the TV service or the database?
Is it really only me this has happened to?