Link can no longer auto-connect to my server

[Banjo H]

I have my Link clients set to /networkclient:<server name>
Until a few days ago, the Link just started up and connected to the server - no prompts.

Now, when link starts up, it give me the error:

"<server name> - The underlying connection was closed: An unexpected error occurred on a send."

This error is at the top of the server selection list and my server is listed. I can select the server and it proceeds normally with no problems. This is on all Link clients.

I have tried:
- retyping the hostname at the client and server
- applying all Windows updates - including some missing .Net ones
- reinstalling the BTV server software

If I start the client with /networkclient:true there are no errors, just a list with my server name.

All Google yields is some ASP development corrections for the error. That would be on SnapStream to include. But, since this just started happening, that doesn't make much sense.

[Banjo H]

I found my problem with a packet trace of the network client start up using wireshark.

The problem is that I recently switched from a private DNS service to Open DNS. It looks like BTV uses a DNS lookup first. Since the host does not exist in DNS, OpenDNS "helpfully" kicks back an IP address for their portal site. BTV then tries to establish a link with that host and fails.

[tscales]

I use OpenDNS on several machines. Never had a problem.