Microsoft Windows Network: The local device name is already in use
I have an issue that just started happening with an ODBC Connection on a Windows 2003 Server (VP1) failing to connect to a database on remote Windows 2008 R2 SQL Server (SQL1).
I received the following error:
ERROR ODBC Database Datasource 'D4TN' [][Named Pipes Provider: Could not open a connection to SQL Server[2], while SQLConnect 08001
Failed to connect to Database using DSN 'D4TN' Err -1
I also noticed that the network shares of the SQL Server are not accessible anymore from 'VP1', I receive the following errors when trying to browse or clicking on the mapped drives:
An error occurred while reconnecting J: to \\SQL1\share
Microsoft Windows Network: The local device name is already in use
This connection has not been restored:
I am still able to browse network shares on 'SQL1' from all other Servers and also have successful ODBC connections to the database D4TN.
I can't ping the 'SQL1' server from 'VP1' and can't ping 'VP1' from 'SQL1', but I can ping 'VP1' and 'SQL1' successfully from other servers.
Please advise on how I can resolve this issue.
I received the following error:
ERROR ODBC Database Datasource 'D4TN' [][Named Pipes Provider: Could not open a connection to SQL Server[2], while SQLConnect 08001
Failed to connect to Database using DSN 'D4TN' Err -1
I also noticed that the network shares of the SQL Server are not accessible anymore from 'VP1', I receive the following errors when trying to browse or clicking on the mapped drives:
An error occurred while reconnecting J: to \\SQL1\share
Microsoft Windows Network: The local device name is already in use
This connection has not been restored:
I am still able to browse network shares on 'SQL1' from all other Servers and also have successful ODBC connections to the database D4TN.
I can't ping the 'SQL1' server from 'VP1' and can't ping 'VP1' from 'SQL1', but I can ping 'VP1' and 'SQL1' successfully from other servers.
Please advise on how I can resolve this issue.
efrimpol
Have your rebooted VP1?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Was there any recent Firewall change or GPO policy update? Ping sometimes doesn't work if is closed by network engineers but telnet to IP PortNumber should work.
Also on VPN1 - try run at command prompts a "tracert <SQL1IP>" to see where connection is "broken"
Also on VPN1 - try run at command prompts a "tracert <SQL1IP>" to see where connection is "broken"
ASKER
Hi All,
I found out the issue. Someone or something had changed of the NIC's TCP settings which had the wrong IP Address entered.
Thanks for your responses.
I found out the issue. Someone or something had changed of the NIC's TCP settings which had the wrong IP Address entered.
Thanks for your responses.
ASKER
Thanks guys