|
|
Posted by Erland Sommarskog on 06/12/06 21:32
pb648174 (google@webpaul.net) writes:
> As per previous posts in this thread, I have added the ping statement
> to the server in question to the backup script.. Here we are a few
> weeks later with the same intermittent
> problem, ping works fine.
>
> Pinging dbserver [192.168.23.154] with 32 bytes of data:
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Ping statistics for 192.168.23.154:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>
> Approximate round trip times in milli-seconds:
>
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> 8:00:19.85
> Timeout expired
> 8:00:37.23
When I was able to get "Timeout Expired" to my server at work, I was
still able to ping my machine.
As I've said before, I suspect that the issue is related to Windows
Networking, Active Directory or something else I have very little
knowledge of.
--
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]
|