SOLVED: Surface Network Adapter dropping connection

Question

Hi guys,

I have been trying to resolve the same issue I currently have with 2 of my surface products; namely the SP3 and the, newly released, Surface Book. The SP3 was my travel companion in the past so didn't pick up this issue until I started to use it, as  a short term fix until my SB was delivered, for my development work.

I basically have my SB connected to the docking station which is connected to 2 monitors and Ethernet for the network. Its pointless information as I have ruled it out as the problem but some insight into setup.

I use SQL Server Management Studio on a daily basis for both development and connecting to my live database servers (via VPN). I initially was connecting using SSMS using SQL Server 2012 version. I have now upgraded to 2016 and installed the, now separate, SSMS component (which is the most currently up to date version). The same error is being experienced regardless of versions; however only when connecting to my live servers and not my database servers on the LAN.

I have searched the Net for solutions and found many insightful issued in the past with Surface network adapters and docking stations. I have eliminated the docking station as the issue as I experience the same problem when not connected to it and using Wi-Fi. I have no issues with connecting using a mobile 4G card so I have to conclude the issue with the network adapter as the same software stack is being used and only the method of gaining access to the internet has changed. I have also targeted the Surface products directly as I have the same software setup on a desktop machine (i.e. windows 10, SQL and SSMS Server, Visual Studio, .NET version, etc, etc) and I have no problem, using a different computer, on the same network I am working on to perform the same tasks (i.e. ruled out the LAN and router network issues).

Basically I connect to the VPN and then log on to one of my database servers using SSMS and SQL Server Authentication. No problem, all good. What happens next within a minute or a couple minutes (random timing with no pattern) after running couple simple scripts and queries to return a very limited dataset (say 100 records) is that I get the following error:

---

Msg 64, Level 20, State 0, Line 0

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

---

I then open new query window and start the process again. I basically have limited query time per query window which degrades each time. I need to restart the application and start the process again.

I have updated the network drivers, Ethernet and Wi-Fi, as well as uninstalled and reinstalled them. I am currently using the latest versions. I have also disabled Energy Efficient Ethernet and Selective Suspend on the Advanced tab of the adapter properties. This did not solve the problem.

To me it seem that the network adapter drops the connection for a brief moment when large data is being transmitted through it. I have recently had large FTP files fail a few times and believe it may be related. It happens in SSMS on every attempt when I try receive large datasets. This is why I am only experiencing the problem in SSMS and not anywhere else.

As I am experiencing the same issue on multiple surface products, which it seems have had some connectivity issues in the past based on previous posts, I assume that the issue may be software related and I am hoping a driver update may be able to resolve the issue.

By the way I have no connectivity issues when going online or using email, etc, etc. Any advice that someone could shed would be highly appreciated; or point me in another direction where the problem could be. I need to resolve this so I can use my SB as my primary work tool.

Thanks,

Conor

Answer 1

UPDATE:

After searching for a solution and going in circles I finally found the problem. And is was not the surface adapter!! I am very happy about this as I was disappointed with the Surface for a little while. That is no longer the case.

Anyhow the actual problem had nothing to do with my computer, which is why I found it difficult to find the solution. It was actually the modem router which was the cause. Again, the problem was only when connected to the VPN and using SSMS to retrieve data or when I RDP into my servers. All other connectivity was fine. I bought a new modem router and all is now running better then ever. The Surface Book is an awesome product once again imho!! :)

cheers,

Conor