At 11:02 AM 4/21/2010, you wrote:
Sounds like a routing problem. Aha, I was going to write a bunch of
stuff, but just realized I was making assumptions of things you
didn't state. So let's clear those up first:
1) First, can devices on the original LAN router access the internet?
yes and at extremely fast speeds. The network, itself is fast and
very reliable for everything except the three TV devices.
2) Since the new N router was set up as a switch, then it's
basically part of the LAN network. So assuming LAN devices on the
original router can access the internet, I don't see why devices on
the new N router wouldn't be able to access the internet since
they're part of the same broadcast domain, and getting the same IPs
as the original LAN devices!
a) So a simple troubleshooting idea: take a device from the
original LAN router and plug it into a switch port on the N router
and see if it can still access the internet. You can also take a
device from the N router and plug it into the original LAN router
and see if it starts working.
The new N switch 192.168.110. is connected to the LAN router
192.168.1.x and has always been able to access the LAN Router and the
internet. It is only the three TV devices that can not, when plugged
in to the new N switch, or even when plugged directly, with a
different cable, into the LAN router.
3) If it's not any of the physical things, then start moving up the
layers, and look at IPs now. Could it be that the new devices are
getting IPs that are somehow not being NAT'ed correctly?
no, because the TV devices all show the correct network numbers that
they find automatically, and they are all correct. I can change them
and set them up manually if I want.
To see if it's an IP issue, you might be able to statically assign
an IP to one of the new devices from a device that can access the
internet from the LAN and see if that makes it start working...
As of yet there is no TV device at any of the numbers assigned to
them that can access the LAN files, or internet through the LAN
router. However, all the TV devices have 192.168.1.x numbers like x=
101 x=106 that must of been assigned to them by the LAN Routers
DHCP. As I wrote, all three TV devices have internal diagnostics to
check for correct setup and connectivity. They always pass their own
diagnostics and connectivity test to the LAN router, but when it
comes to accessing the internet, and in the case of the WD live, the
LAN itself, I can not access anything.
I usually end up with a error message like, can not find DNS
server... but the numbers they show in their own IP setups are always
correct to COX DNS server on the WAN. But when I plug the cable going
from the TV device directly into the WAN router... boom I'm online.
This approach is fine with the TV and the BRD player, because
Vericast only accesses online content, but not the WD live media
player as it needs to access to the LAN files. I hope this makes it
clearer and thanks for the input.
w
There's more but that's a good start for now; I mean, at the start
it seemed like it was just a routing problem where packets don't
know how to get back to the LAN from the WAN, but you haven't given
enough information about the setup to be sure of that...hehe, you
don't have a Visio of the network do you?! :P
BINO
> Date: Tue, 20 Apr 2010 21:05:58 -0700
> To: [email protected]
> From: [email protected]
> Subject: [H] Network issue
>
> I have a new TV and BRD player with Panasonic on line Vericast
> capability. Unfortunately, there is a issue with my network setup. I
> have figured out a work around but I don't particularly like it. My
> Network is setup to isolate the WAP from my LAN, I give access to
> employees as well as friends, and family but I do not want them to
> even see my LAN. So I use three older Linksys stacked routers. Cox
> cable is plugged into a Motorola Surfboard 2 which is plugged into
> the WAN 192.168.3.x which is a wired router. The LAN 192.168.1.x is a
> wireless router with wireless disabled. The WAP 192.168.2.x is a
> wireless router. The routers are setup with three different IP
> numbers. The LAN and the WAP are plugged into the WAN.
>
> There are lots of stuff running off the LAN, a couple of network
> printers, a couple of 10/100/1000 switches, a 10/100 switch. This
> setup has run for years, and while I had to screw with it to get it
> going, once I had it setup, it has been running flawlessly for years
> now. I never have to reboot or shut it down. It never gives me a
> single problem. It works like things should work.
>
> I am in the process of setting up two additional routers as simple
> access points. One to extend the range of the existing WAP, which is
> not a problem .... and a new N router which will be for my personal
> use connected to my LAN and operating as a switch for my TV, BRD and
> a WD Live media player. This is the one Greg helped me setup as a
> simple switch and access point.. no DHCP, no firewall.... and it works.
>
> But my TV, BRD and WD Live can't function correctly when plugged into
> it. When plugged into the switch all three see, and correctly ID the
> LAN the COX numbers, and can even pass their internal network
> test... but when I want to get out to the internet, or access my LAN,
> it can not find it's way out, and I typically get a DNS server not
> found error.
>
> To troubleshoot, I worked my way back, one wire, one connection, one
> switch, one router at a time until it worked. This happened
> instantly when I plugged the TV, BRD and WD live directly into the
> WAN. The TV and the BRD don't need to access my LAN so I could solve
> that problem just by running CAT 5e cable directly from the WAN to
> those devices. However, the WD live needs to work with my LAN in
> order to access media. It also needs to access the internet for
> updates, and services such as Netflicks.
>
> Apparently, something is blocking DNS Server access from the TV, BRD
> and the WD Live and keeping them from accessing the internet when
> plugged into the LAN, and in the case of the WD Live my shares. Any
> ideas on solving this?
>
> Thanks.
>
> w
>
