Server does not support RFC 5746, see CVE-2009-3555 What does it mean and what should I do?

MOVED YOU TO TELEVISION
THE post means wifi failure.
first off do all things wifi fail in home? or just this TV>
PCs fail, and Cell phones on wifi fail>????

where did slingshot come from,. somebody put it there ask them to make it work, your service provider put it there
and did you know many slingshot routes are INFECTED.
2012 up
"The exact attack vector is not clearly known, though the Slingshot APT is known to utilize CVE-2007-5633, CVE-2010-1592, and CVE-2009-0824 "

all I and do is guess, below, location, and routers model not told.
are you in New Zealand post here to N.America.?
who is your ISP, and what modem/router did they put in your home.
one of these in NZ'
NF18 Fibre NF18 ADSL/VDSL + Homeline NF18 ***** VDSL NF4V ADSL/VDSL + Homeline
if yes call them in NZ ,your ISP read you billing for phones to call.
and ask too if infected. modem it is.
ask them not N.American fixya.

no country told
no modem/router told.
no TV model told
basically no way to answer lacking facts and blinded in a text box.

when posting be sure to tell country first.
and ISP and what modem/router you have first
so we can tell you who can fix this.
or call your ISP they surely will.

Is the software designed to work with Windows 8? Check the Windows website to see if it is.

I really don't know what to do next, i suppose the easiest solution is to forget my money and stop using paypal any more as i think that I am not getting anywhere answering question after question and getting no further forward. thank you.

RFC-822 is a text formatting standard. There are many, many RFC rules. This particular one is a rather old rule about text formatting on ARPA net. May be generated by an old system or the error may be such that the system generating it doesn't know what else to call it.

!??

RFC is Request For Comments on network protocols of all types.

This means that the server has received the request headers, and that the client should proceed to send the request body (in case of a request which needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the requests headers alone, a client must send Expect: 100-continue as a header in its initial request (see RFC 2616 14.20 Expect header) and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).

Technical Specifications AAL and ATM Support
VCI 0-65535 address range
VPI 0-255 address range
AAL5 support
Bridging
IEEE 802.1.d Transparent Learning Bridge (dynamic learning of up to 255 addresses)
Spanning Tree support
Certifications
FCC Part 15, Class B
CE certification
Connectors
DSL interface: RJ-11 or RJ-45 (Europe)
Ethernet interface: RJ-45
USB Type B interface (5200, 5500 series)
Diagnostic LEDs
Power, DSL, Activity, Ethernet status; USB status (5200, 5500 series)
Management
Intuitive, Web-based GUI management access
SNMP support
Comprehensive hardware diagnostics
Media Interface
RJ-11 or RJ-45 (European) DSL WAN connection
10/100Base-T RJ-45 Ethernet LAN connection
USB Type B LAN connection (5200, 5500 series)
Power
12V power supply included, 700ma max. 5400/5500 - 12 VDC, 1000ma max.

Routing
DHCP server/DHCP client
Network Address Port Translation (NAPT)
Network Address Translation (NAT)
Packet filtering
RFC 2364 Point-to-Point Protocol over ATM PVCs (PPPoA)
RFC 2516 Point-to-Point Protocol over Ethernet (PPPoE)
RFC 2684 (formerly 1483) Bridged Ethernet and routed encapsulation Routing
Standards Compliance
IEEE 802.3
USB 1.1 T1.413 issue 2 G.992.1 (G.DMT) G.992.2 (G.Lite)

Hello.

Yes they generally refer to load balancing on different servers however that does vary per website. This method is usually only found on high-traffic websites.

Hope that helps!

The DSL-500 supports RFC-1483, 1577, 2364, and 2516.