P
prophead
A couple of weeks ago I suddenly started getting the error message "no such
interface" when attempting to connect to SQL Server from an ADP on my LAN.
The port is correct and I tried every trick I could think of with client and
network configuration but could not get it to connect until I enabled Named
Pipes. The TCP/IP connection simply stopped working.
Now I have a client who suddenly has the same problem. I would simply get
them connecting via Named Pipes and move on, except they have a Web app that
needs to come in from the Internet to their SQL Server over TCP port 1433.
What could cause the TCP network library to stop working?
interface" when attempting to connect to SQL Server from an ADP on my LAN.
The port is correct and I tried every trick I could think of with client and
network configuration but could not get it to connect until I enabled Named
Pipes. The TCP/IP connection simply stopped working.
Now I have a client who suddenly has the same problem. I would simply get
them connecting via Named Pipes and move on, except they have a Web app that
needs to come in from the Internet to their SQL Server over TCP port 1433.
What could cause the TCP network library to stop working?