[cvsnt] Re: Lockserver on Loopback?

Glen Starrett grstarrett at cox.net
Wed Feb 11 14:19:18 GMT 2004


Bo Berglund wrote:

>Are we talking about the same thing?
>The Microsoft LoopBack Adapter is what I mean. It is not installed 
>by default and if you want your laptop to retain the TCP/IP protocol 
>even when you pull the plug on the network cable it is essential. 
>
>If no network adapter is present when the LAN cable is pulled then 
>Win2000 and up will unload the TCP/IP protocol and you cannot use 
>any socket communication within the PC itself anymore.
>
>So sometimes you need to have it installed (I do). But to install 
>it menas going to Add/Remove Hardware and go though the guide and 
>manually select the network card, then Microsoft then LoopBack Adapter.
>This installs it onto the system. After this you have to give it a 
>sensible IP address too, just like you do the other NICs, except 
>this one will never see a DHCP server of course.
>
>When we have this adapter enabled on our production PC:s in addition
>to a real NIC on the customer's network we get these delays in 
>communication that breaks our SQLServer calls. Disabling it cures those 
>delay issues.
>
>  
>
Perhaps a bit off topic, but it sounds very odd to need a loopback 
adapter on a production machine.  Are they not always connected?  If 
it's causing trouble, then yank it!  You can always use the loopback 
*address* without trouble, correct?  Perhaps if you disabled the TCP/IP 
binding on that interface it would have the same effect as removing it, 
but since I have no idea why you would need it I don't know if that 
would work or not for you.

It sounds like what you're looking for is some way to specify which 
adapter LockServer / CVSNT binds to. 

--------------------
Glen Starrett






More information about the cvsnt mailing list