Problems logging in to Azure from SSMSImpossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12Insert into … values ( SELECT … FROM … )How to return only the Date from a SQL Server DateTime datatypeHow to concatenate text from multiple rows into a single text string in SQL server?How to connect to local instance of SQL Server 2008 ExpressHow do I UPDATE from a SELECT in SQL Server?Unable to connect SSMS, Microsoft SQL Server, Error: 53Use SQL Server Management Studio to connect remotely to an SQL Server Express instance hosted on an Azure Virtual MachineMake SQL Server on Azure server available locallySSMS connect to azure failureSSMS - Unable to connect to SQL Server 2017 Express on Azure VM using SSMS on local computer
ATMEGA328P-U vs ATMEGA328-PU
How is it possible for tall trees to pull water to heights more than 10m?
Does friction always oppose motion?
Calculus, water poured into a cone: Why is the derivative non-linear?
How do I tell my girlfriend she's been buying me books by the wrong author for the last nine months?
How do I present a future free of gender stereotypes without being jarring or overpowering the narrative?
Could you fall off a planet if it was being accelerated by engines?
What would you need merely the term "collection" for pitches, but not "scale"?
Why am I getting an electric shock from the water in my hot tub?
Five 5-cent coins touching each other
Why are examinees often not allowed to leave during the start and end of an exam?
How useful would a hydroelectric power plant be in the post-apocalypse world?
What was the point of separating stdout and stderr?
How does mmorpg store data?
What are the children of two Muggle-borns called?
Does "boire un jus" tend to mean "coffee" or "juice of fruit"?
How to track mail undetectably?
Why are symbols not written in words?
Where to connect the fuse and why?
Why was Pan Am Flight 103 flying over Lockerbie?
Is there a word for the act of simultaneously pulling and twisting an object?
What is this fluorinated organic substance?
Why would Dementors torture a Death Eater if they are loyal to Voldemort?
Cat files in subfolders in order given by a list
Problems logging in to Azure from SSMS
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12Insert into … values ( SELECT … FROM … )How to return only the Date from a SQL Server DateTime datatypeHow to concatenate text from multiple rows into a single text string in SQL server?How to connect to local instance of SQL Server 2008 ExpressHow do I UPDATE from a SELECT in SQL Server?Unable to connect SSMS, Microsoft SQL Server, Error: 53Use SQL Server Management Studio to connect remotely to an SQL Server Express instance hosted on an Azure Virtual MachineMake SQL Server on Azure server available locallySSMS connect to azure failureSSMS - Unable to connect to SQL Server 2017 Express on Azure VM using SSMS on local computer
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
sql
azure ssms asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
add a comment |
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
sql
azure ssms asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
add a comment |
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
sql
azure ssms asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
sql
azure ssms sql
azure ssms asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
edited Mar 27 at 6:48
mjordan
asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
asked Mar 25 at 16:37
mjordanmjordan
961 silver badge11 bronze badges
961 silver badge11 bronze badges
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName@myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
|
show 5 more comments
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55342534%2fproblems-logging-in-to-azure-from-ssms%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName@myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
|
show 5 more comments
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName@myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
|
show 5 more comments
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName@myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName@myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
edited Mar 28 at 19:55
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
answered Mar 25 at 16:52
granadaCodergranadaCoder
15.7k5 gold badges56 silver badges84 bronze badges
15.7k5 gold badges56 silver badges84 bronze badges
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
|
show 5 more comments
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Thank you for your reply. I did try that, but it didn't make a difference. TCP work fine if I have the wired interface enabled, but fails if the wired interface is disabled even though the wireless is enabled and working. Firewall rules seem to work fine on either interface using sqlcmd. I even tried turning off Firewall completely and get the same results. I edited my question to add that information.
– mjordan
Mar 27 at 6:47
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Gaaaaaaaaaaaaaaaaaaaaaaaaaaa. That stinks. I'll give you one more helper hint. Get this program, and this lets you just ping the machine/port without any middleman (sql-server is the middle man here). microsoft.com/en-us/download/details.aspx?id=24009 "PortQryUI - User Interface for the PortQry Command Line Port Scanner" Good luck.
– granadaCoder
Mar 27 at 13:26
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
Thanks. I got a positive response from PortQryUI on both wired and wireless connections (TCP port 1433 (ms-sql-s service): LISTENING portqry.exe -n gobo.database.windows.net -e 1433 -p TCP exits with return code 0x00000000.) The only other information I can offer is that using ADO.net from VS2017 gives me the same error if wired Ethernet is disabled. Yes, I have tried all kinds of different login combinations. tcp:myazuresqlservername.database.windows.net,1433 is one I've been using. I am left with reformatting my machine again and never connecting to wired ethernet as the only solution.
– mjordan
Mar 28 at 14:21
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
One more poor man's hint/tip. Try to connect using a Control Panel / Admin Tools/ ODBC / System DSN (or User DSN, either DSN). Picking sql-server of course. a DSN connection is a less intense middle-man than SSMS. If that works (and you know portqueryUI works)..then you have high confidence SSMS is the culprit.
– granadaCoder
Mar 28 at 14:41
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
Thanks. In both wired and wireless connections I get: "Microsoft SQL Server ODBC Driver Version 10.00.17763 Running connectivity tests... Attempting connection Connection established Verifying option settings Disconnecting from server TESTS COMPLETED SUCCESSFULLY!"
– mjordan
Mar 28 at 16:06
|
show 5 more comments
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
add a comment |
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
add a comment |
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
answered Apr 4 at 18:52
mjordanmjordan
961 silver badge11 bronze badges
961 silver badge11 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55342534%2fproblems-logging-in-to-azure-from-ssms%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
