In my last post I told you how to change the interface metric from command line if your Ptcl smart tv is not working on your pc.
In this post I will tell you how to change the interface metric from GUI.
Howtos and Tutorials from behind the firewall
In my last post I told you how to change the interface metric from command line if your Ptcl smart tv is not working on your pc.
In this post I will tell you how to change the interface metric from GUI.
If you has multiple interface on your PC then chances are multicast streaming (like iptv PTCL smart tv pc application) will not work on your pc.
Most of the peoples who has the multiple interface like lan card wifi connected on the same time complains ptcl smart tv not working on their pc.
The reason behind this problem is your video player is send multicast packets to the wrong interface. To solve the problem simply follow these steps.
Run cmd .
If you has Windows vista or later then right click on the cmd and run as administrator.
Enter the following command on the cmd to check the interface name and metric
netsh interface ipv4 show interface
output will be like this.
After a recent Windows Update I could no longer access the folders on my Windows XP file server. A window popped up asking for a username and password even though they are both the same on the two computers. The error message each time was “Logon failure: unknown username or bad password.”
I typed in my username and password five times. It reached the point where I thought I had gone crazy and was typing in the wrong one: it kept on coming back to me with the dreaded “Logon failure: unknown username or bad password.”.
I quickly returned to my senses and guessed something was up with the authentication between XP and Windows 7. A few Google searches later I found out that a Local Security Policy needs changing.
It seems that a recent Windows Update has changed that policy’s settings to be undefined, which —from what I can tell— forces NTLMv2 session security always. My XP installation mustn’t have NTLMv2 capability and that is why I kept seeing “Logon failure: unknown username or bad password.” errors.
After changing the local policy I was immediately able to connect to my network shares again.