Video Asylum

TVs, VCRs, DVD players, Home Theater systems and more.

Use this form to submit comments directly to the Asylum moderators for this forum. We're particularly interested in truly outstanding posts that might be added to our FAQs.
You may also use this form to provide feedback or to call attention to messages that may be in violation of our content rules.

You must login to use this feature.

Inmate Login

By default, logging in will set a session cookie that disappears when you close your browser. Clicking on the 'Remember my Moniker & Password' below will cause a permanent 'Login Cookie' to be set.

Moniker/Username: The Name that you picked or by default, your email. Forgot Moniker?	Examples "Rapper", "Bob W", "joe@aol.com".
Password:	Forgot Password?
	Remember my Moniker & Password ( What's this?)

If you don't have an Asylum Account, you can create one by clicking Here.

Our privacy policy can be reviewed by clicking Here.

Inmate Comments

From:
Your Email:
Subject:

Message Comments

Original Message

RE: It sounds like a bug or router setup....

Posted by Cut-Throat on May 5, 2017 at 09:43:46:
I was on a Network Forum about this problem, and there was a guy on there that used to write code for routers and has come across this problem before.

Apparently there are some routers and devices that don't always 'play well' together. And some TV manufacturers have 'strayed from standards' to accommodate different Network devices. He also said there was a lawsuit a while back involving TP-Link, that caused a lot of Manufacturers to start going 'By the Book'

He said, since it is a new TV, Samsung has probably written their code "By the Book", and that may be the problem I am experiencing.

At any rate, I have manually assigned a fixed IP address, so that I have a good work around for the problem.

Most users don't even look at their IP addresses on their network, so the problem is not widely known.