[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.
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.
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.
- In Windows Explore, navigate to C:\Windows\System32\drivers\etc
- Open the Hosts file with Notepad.
- Create the following entry at the end of the file: IP-address Computer-Name
- Save and close the file.
- To check the functionality, repeat step 1.
- Open a Windows Command Prompt and type Ping
IP-address to determine connectivity with the
- To perform a reverse DNS lookup, type Ping -a
The computer should resolve the command immediately.