February 3, 2004 at 8:45 am
Strange database problem.
I have 2 servers one running as webserver and the other as Database server running MSSQL 2000 SP3.
They are connected i 2 ways. Through a public net using static IP and through a direct cable using another IP.
My problem is that I cannot connect to or from the database through the crossed cable (I run a DTS which imports a zipped access file from an FTP account on the webserver).
Running through the public net works fine but not through the crossed/direct cable.
All other connecting (ping, filesharing, FTP not through DTS, etc) works fine through that cable but ODBC connections from the webserver don't and neither does DTS access from the database server.
Does anyone have a clue.
------------------------------------------
Did you know that if you don't drink your milk every morning, the Arla-rabbit will come and shoot you in the head, or sometimes in the belly?
February 3, 2004 at 9:37 am
Was this cable/IP added since the last time SQL Server was restarted or the server rebooted? I've had issues where the listener for SQL Server doesn't dynamically pick up new IPs. Try a netstat -a from either machien and be sure that there is a SQL Server listener on 1433 or whatever port you're selected.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
February 4, 2004 at 2:12 am
Thanks a lot, the problem solved itself when I restarted the webbserver. It seems like you where on the right track.
------------------------------------------
Did you know that if you don't drink your milk every morning, the Arla-rabbit will come and shoot you in the head, or sometimes in the belly?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply