-cmi.com
-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: 10 March 2009 19:10
To: NT System Admin Issues
Subject: Re: DNS / WINS Issue?
On Tue, Mar 10, 2009 at 11:22 AM, Kevan Dickinson
wrote:
> If I ping the FQDN I get the correct resolved address.
> If I pin
On Tue, Mar 10, 2009 at 11:22 AM, Kevan Dickinson
wrote:
> If I ping the FQDN I get the correct resolved address.
> If I ping just the netbios name of the machine I get the wrong IP
> address returned.
Check hosts (DNS) and LMHOSTS (NetBIOS) files.
Run NSLOOKUP (or better yet, DIG.EXE from I
: Steph Balog [mailto:validemai...@gmail.com]
> Sent: 28 February 2009 11:38
> To: NT System Admin Issues
> Subject: RE: DNS / WINS Issue?
>
> Ahhh, (i see say the blind man as he tripped over is cane and saw) ;-)
> You issue isnt really sql at all, nor is it dns so much. You are a
-cmi.com
-Original Message-
From: Steph Balog [mailto:validemai...@gmail.com]
Sent: 28 February 2009 11:38
To: NT System Admin Issues
Subject: RE: DNS / WINS Issue?
Ahhh, (i see say the blind man as he tripped over is cane and saw) ;-)
You issue isnt really sql at all, nor is it dns so much
Ahhh, (i see say the blind man as he tripped over is cane and saw) ;-)
You issue isnt really sql at all, nor is it dns so much. You are a victim of
one of MS's better TCP/IP stack designs (no really, it is a better design).
MS did a great thing is the use of caches when it does its network lookups
14:03
To: NT System Admin Issues
Subject: re: DNS / WINS Issue?
What *could* be happening when your user drops connection and tries to
reconnect to a naned pipe session, sql server is picking it up and
trying to reconnect to the "sleeping" process it left behind. And
because the IP has ch
What *could* be happening when your user drops connection and tries to
reconnect to a naned pipe session, sql server is picking it up and trying to
reconnect to the "sleeping" process it left behind. And because the IP has
changed even though you use named pipes to connect, I guess it kind of lo
