vague disconnect issue on server
-
Ok, I have a windows server 2008 r2 running sql server 2008 r2. 64 bit. We are having a weird issue where all connections are dropped randomly and regularly. Sometimes it comes back within a few seconds, sometimes it takes 20 minutes. This means that RDP disconnects, SQL reporting web page is unavailable, etc...But Great Plains connection(From a client computer) through an ODBC still works. The weird part is, there are no errors in any logs that correlate to it time wise, and when the disconnect happens, you can ping the server all day long with no dropped packets. On top of that, while unable to connect via rdp or anything else, you can go to the console on the stinking thing and get out to the internet, network, anywhere you wish to go. To make matters worse, I have one HyperV virtual machine running on that server. You CAN RDP to that VM while NOT being able to rdp to the main server that is the host. ie.. SQLSERVER is the main physical server, WEB1 is the VM. While not being able to connect to anything on SQLSERVER, I can RDP to WEB1. Any clues as to where to even begin to look at this? Has anybody ran into anything similar to this before?
Treat stressful situations like a dog, if you can't eat it, play with it or screw it, then just piss on it and walk away. Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow.
-
Ok, I have a windows server 2008 r2 running sql server 2008 r2. 64 bit. We are having a weird issue where all connections are dropped randomly and regularly. Sometimes it comes back within a few seconds, sometimes it takes 20 minutes. This means that RDP disconnects, SQL reporting web page is unavailable, etc...But Great Plains connection(From a client computer) through an ODBC still works. The weird part is, there are no errors in any logs that correlate to it time wise, and when the disconnect happens, you can ping the server all day long with no dropped packets. On top of that, while unable to connect via rdp or anything else, you can go to the console on the stinking thing and get out to the internet, network, anywhere you wish to go. To make matters worse, I have one HyperV virtual machine running on that server. You CAN RDP to that VM while NOT being able to rdp to the main server that is the host. ie.. SQLSERVER is the main physical server, WEB1 is the VM. While not being able to connect to anything on SQLSERVER, I can RDP to WEB1. Any clues as to where to even begin to look at this? Has anybody ran into anything similar to this before?
Treat stressful situations like a dog, if you can't eat it, play with it or screw it, then just piss on it and walk away. Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow.
-
Hi, What type of router is the server behind? I have seen similar behavior on cheap Linux based routers where it was a ip_conntrack issue. Best Wishes, -David Delaune
dell poweredge switches going to a watchguard XTM525 firewall that is less than 6 months old. The firewall handles all routing and dhcp. The server is not on dhcp it is on a static. There have been a couple strange firewall/dhcp issues lately as well, is it possible the routing is screwing up do you think?
Treat stressful situations like a dog, if you can't eat it, play with it or screw it, then just piss on it and walk away. Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow.
-
Ok, I have a windows server 2008 r2 running sql server 2008 r2. 64 bit. We are having a weird issue where all connections are dropped randomly and regularly. Sometimes it comes back within a few seconds, sometimes it takes 20 minutes. This means that RDP disconnects, SQL reporting web page is unavailable, etc...But Great Plains connection(From a client computer) through an ODBC still works. The weird part is, there are no errors in any logs that correlate to it time wise, and when the disconnect happens, you can ping the server all day long with no dropped packets. On top of that, while unable to connect via rdp or anything else, you can go to the console on the stinking thing and get out to the internet, network, anywhere you wish to go. To make matters worse, I have one HyperV virtual machine running on that server. You CAN RDP to that VM while NOT being able to rdp to the main server that is the host. ie.. SQLSERVER is the main physical server, WEB1 is the VM. While not being able to connect to anything on SQLSERVER, I can RDP to WEB1. Any clues as to where to even begin to look at this? Has anybody ran into anything similar to this before?
Treat stressful situations like a dog, if you can't eat it, play with it or screw it, then just piss on it and walk away. Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow.
Two things to try. 1. Assign a static IP locally, with a DHCP reservation w/ MAC binding if possible. 2. Check the TTL on your IP Address. I've known short DHCP lease times to cause a fit if the scope is well used. Can you perform a PING -t at the server while it's having RDP issues? If the PING stays good, I'd look for a userprofile timeout, as it can be extremely slow on over-taxed SQL boxes. This can keep you from being able to RDP into it, while the data streams can usually access it with no issue.
Something worth reading, albeit it's invincible!
-
Two things to try. 1. Assign a static IP locally, with a DHCP reservation w/ MAC binding if possible. 2. Check the TTL on your IP Address. I've known short DHCP lease times to cause a fit if the scope is well used. Can you perform a PING -t at the server while it's having RDP issues? If the PING stays good, I'd look for a userprofile timeout, as it can be extremely slow on over-taxed SQL boxes. This can keep you from being able to RDP into it, while the data streams can usually access it with no issue.
Something worth reading, albeit it's invincible!
it was assigned a static IP from day one of being setup. All of my servers are. turns out, I think it was a DHCP issue. Somebody adjusted one of the ranges so that it overlapped the ip of that server... On top of that, the reservation I had set(just in case) was removed as well. So another machine got that IP and caused no end of confusion... I fixed the dhcp ranges and the issue seems to have went away. No, I did not kill the guy that did it, yet.
Treat stressful situations like a dog, if you can't eat it, play with it or screw it, then just piss on it and walk away. Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow.