I am having issues with my client computers randomly not connecting to server. I am running SQL Express 2012.
When clients are not connecting to server, I can fix the issue by disabling and enabling network adapter on server and clients connect again. This seems to happen every couple of days.
Network and Power Options are setup for computers not to go to sleep. BIOS and Network Driver are updated to latest available from manufacture. OS is Windows 8.1 Home.
I understand this is network related issue. I will need to replace Ethernet cable, Switch or Server.
Based on logs below from one of the client computers what do you guys this I should replace.
It seems log file might have wrong timestamp. This client computer was crashing around 12:38 PM, but it is recorded as 7:38 PM on 12/6/2014. I checked the time on the computer and it is correct. Right now, time is 2:45 PM 12/6/2014 .
Router leases expire after 1 day. I have the POS connected to a switch and switch is connected to router. All computers are set with static IP addresses so leases should not expire.
I think the issue is isolated to server computer. Server network card seems to go offline somehow. If I disable and enable server network card everything starts working again.
Other computers are working properly because I can ping 8.8.8.8 from other compters, but not from server.
do you have error logs enabled for the server? Can maybe identify some issues more precisely. Maybe look at the Event Viewer it should give an idea of whats happening.
Honestly it doesn’t sound like a hardware issue… sounds more like software. Probably a configuration issue. or conflict.
A hardware issue typically wouldn’t behave that way. Furthermore a hardware issue would show signs of failure. Something would show up in error logs or event viewer.
How has this been going for you? I like to know every problem possible so that If I personally ever see it I can diagnose it quickly. Did you also set static ip’s to all computers including server? @na1978
Anyone using Comcast should probably look into a current lawsuit happening against them right now. You may already know but Comcast is pushing out a City Wide WiFi initiative to offer WiFi to more people. One of the ways they are expanding their coverage is by including a 2nd internet channel in their modem’s/routers which when turned on effectively means they are using your router as a WiFi hub for their new initiative.
This is one of those routers that has xfinity public WIFI. What makes it worse is that this router is really under-powered. Pinging Comcast modem from my client computers I was getting 10-15 ms response time and this was in the middle of the night without any other clients connected. Image if I had 3-5 people streaming Netflix. I called Comcast and they agreed to replace it a different model.
Linksys router is 1 ms response time from same computers.
Not sure if any tweaks would have fixed my problem. The network adapter was dropping. I could not ping server or go online. I have never seen this before. Disable and enable would bring network adapter back to life. LOL.
Can you share the link for TCP tweaks? I am sure it might help me somewhere down the road.
Sorry that was meant for a different thread and I just realized I put it under wrong one lol. I was reading yours and the other one at same time today must have gotten replies mixed up.
Since you asked however there are advanced tweaks to the TCP configuration of SQL server that you can do that specifically pertain to connections and keeping them alive. I lost the article I was reading and its not something I have actively looked at recently let me see if I can dig it up.
Here is a starting point: This is for advanced users and should tread lightly if your not sure.
Start the SQL Server Configuration Manager mmc snap-in and navigate to your TCP/IP protocols and look for the setting Keep Alive. This parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet to its peer. The default for this is 30000ms
If the remote system is still reachable and functioning, an acknowledge packet is sent back and the connection stays alive. If no acknowledge packet is received. The server will send a Keep Alive packet in an interval 1000ms for TcpMaxDataRetransmissions (default 5) times. During this time the connection will still be saved if an acknowledge arrives. With no acknowledge the connection gets reset.
You can configure TcpMaxDataRetransmissions in the registry under HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
This is for advanced users and should tread lightly if your not sure.