|
Posted by Erland Sommarskog on 10/02/76 11:48
pb648174 (google@webpaul.net) writes:
> We have multiple database servers and want to keep it centralized so I
> don't think we will do the back job from the SQL Server.. Also, that
> doesn't seem to make sense because all osql or enterprise manager does
> is issue a command to the SQL Server.. It isn't actually making a
> backup from the connecting client and transferring the file. I guess
> for now we will just live with the intermittent backups problems. I
> have the ping command in there so I'll know once it fails again if the
> entire network connection is down.
The error "timeout expired" has nothing to do with the backup command.
You could just as well have a "PRINT 'Howdy!'" in that input file. You
would get the same error. OSQL fails to connect to SQL Server for some
reason that I don't know.
> Erlans, I take it you have unblocked ALL traffic to 1433 for your
> firewall? It might consider your home connection as a different type of
> connection. Also, I have had problems with Authenticated logins through
> firewalls and use only SQL Authentication when just 1433 is open.
It used to work, but then I installed this Internet Firewall Client. There
is some ISA Server in the mix too. I have not investigated where the
problem might be, and I think I will leave to my sysadmin to find out. :-)
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|