[KBA-01014] Omnicast™ DirectShow Filter cannot connect to a remote Gateway - Omnicast™ 4.0 - 4.8

series
Omnicast™ 4.0 - 4.8
revised_modified
2013-03-08

[KBA-01014] Omnicast™ DirectShow Filter cannot connect to a remote Gateway

This article explains why the Omnicast™ DSF (DirectShow Filter) cannot connect to a remote Gateway.

Symptoms

The Omnicast™ DirectShow filter cannot connect to a remote Omnicast™ Gateway. However, a successful connection is established when pointing it to local Omnicast™ Gateway. Using the omnp:// url in Windows Media Player does not work either.

For more information about using the DSF, see [KBA-00053] Installing and Using the Omnicast DirectShow Filter.

Cause

This issue can occur after an upgrade or a new installation because the Omnicast™ DSF creates an entry in the Windows Registry after the connection with the Omnicast™ Gateway is established.

During the connection process, the DSF performs a reverse DNS call before trying to connect. For instance, it tries to resolve IP: 10.12.17.25 into the computer's name: MainGateway.

If for some reason the reverse DNS lookup takes longer than expected, the DSF connection will time out. This behavior also occurs when using an IP address because a reverse DNS is always performed.

Workaround

To prevent this issue from happening, you can edit the Windows host file as follows:
  1. In Windows Explore, navigate to C:\Windows\System32\drivers\etc
  2. Open the Hosts file with Notepad.
  3. Create the following entry at the end of the file: IP-address Computer-Name
  4. Save and close the file.
  5. To check the functionality, repeat step 1.
To determine whether the reverse DNS lookup is performed properly:
  1. Open a Windows Command Prompt and type Ping IP-address to determine connectivity with the device.

  2. To perform a reverse DNS lookup, type Ping -a IP-address.

    The computer should resolve the command immediately.