On Friday 23 April 2010 23:33:50 Winterlight wrote:
> OK, now I have replaced that router = Linksys WG54 with another
> Linksys WG54 that I updated the firmware on and checked it out as
> working well. Then I set it up for my Network = DHCP at defaults
> 192.168.1.1, disabled wireless completely, g
I'd say that's likely part of it!
On 4/24/2010 3:36 AM, Gaffer wrote:
On Friday 23 April 2010 23:33:50 Winterlight wrote:
OK, now I have replaced that router = Linksys WG54 with another
Linksys WG54 that I updated the firmware on and checked it out as
working well. Then I set it up for my Netwo
My problem with that is AFAIK, he has other devices on the LAN that are working
fine (getting NAT'ed to the outside, though I may be wrong about that), whereas
it's just the TV devices that don't work-the difference with them is that
they're "new" which makes me think it's something else, but i
At this point (w/o doing the actual troubleshooting session) I'd say
that you just collapse your networks into one flat 192.168.1.x (you
don't need multiple networks anyway-not like you're firewalling and
enforcing security policies b/w them anyway, are you?)
I do need them, because I have e
http://gedebeq.tripod.com/
Spam? Virus? Seems like an odd post!
On 4/24/2010 7:05 PM, al wrote:
http://gedebeq.tripod.com/
So are you firewalling the WAP or just using a separate IP range?
Worse comes to worse, assuming you are double NAT'd with the WAP doing DHCP for it's
subnet. I'd setup the WAP as Gateway, DNS & DHCP server and it's DNS client pointing
to gateway router. This should properly forward DNS request
