K
karlhfr
So we use windows server 2016
we have just moved business address and now i am having issues with connecting from outside the network. We use a stock system that is on the server, and i can have this software at home and remotely login using the public ip address and sql user credentials. I also use windows remote desktop.
Since we have moved, i have changed the remote desktop app ip address so i can still connect to the server from home, but it disconnects and reconnects every 20 seconds or so. (sometimes longer, sometimes shorter)
we also have the disconnects from the software that i have used from home.
the only error i can see is the software says
'There was a problem retrieving the data: a transport-level error has occurred when receiving results from the server (provider: TCP provider error: 0 - The semaphore timeout period has expired)
i have oped ports 1433 & 3389. I have also swapped the bt hub back to the one we used at our old address and get the same issue. So im guessing that its an issue on the server.
I also do not get this issue when i remote in to the server on the local 192 IP address
PLEASE HELP!
Continue reading...
we have just moved business address and now i am having issues with connecting from outside the network. We use a stock system that is on the server, and i can have this software at home and remotely login using the public ip address and sql user credentials. I also use windows remote desktop.
Since we have moved, i have changed the remote desktop app ip address so i can still connect to the server from home, but it disconnects and reconnects every 20 seconds or so. (sometimes longer, sometimes shorter)
we also have the disconnects from the software that i have used from home.
the only error i can see is the software says
'There was a problem retrieving the data: a transport-level error has occurred when receiving results from the server (provider: TCP provider error: 0 - The semaphore timeout period has expired)
i have oped ports 1433 & 3389. I have also swapped the bt hub back to the one we used at our old address and get the same issue. So im guessing that its an issue on the server.
I also do not get this issue when i remote in to the server on the local 192 IP address
PLEASE HELP!
Continue reading...