Eben King wrote:
> On Tue, 30 May 2006, Kwan Lowe wrote:
>
>>> So then, what changes do I have to make? Add rules on router #2 to
>>> get the
>>> services I want on LAN #1. (What ports does Samba use?) What else?
>
>
> I can't find the "virtual servers" list, even though I swear I've seen
> it before. I did find "port forwarding", which a net source claims is
> the same thing.
>
>> Changes you'd need to make:
>>
>> 1) On router 2, allow TCP 137/139.
>
>
> With or without that, the workgroup appears empty, but I can call up my
> Samba server by Start -> Run... \\192.168.1.11\ . So the data path is
> working at least.
>
> I added the rule, but it refers specifically to 192.168.2.64 (my
> laptop). That won't do anything for other machines hanging off router
> #2. Nothing in the workgroup, but maybe the announcement hasn't been
> made yet.
>
> Allow TCP 22 for SSH. HTTPD is TCP/80 but this is generally on by
>
>> default.
>>
>> 2) If you're running recent versions of software on "pc", keep in mind
>> that some services won't work unless "pc" can resolve IPs in your /25
>> subnet.
>
>
> Adding them to /etc/hosts should suffice, yes?
>
> Actually, the router assigns static addresses for all it gives out by
> DHCP, and it's in general a caching nameserver, so it _should_ give out
> those machines' addresses. Dunno what names they'll get though.
>
It won't work because you are on different broadcast domains. If you ran
a WINS server then they should be able to resolve the hostname (provided
the clients know about the WINs server. But you still won't be able to
browse the workgroup.
Honestly I see no valid reason for you to configure your network like
that. You are adding complexity and making it un-user friendly.
I believe you should:
1. plug one of the netgear's switch port into the DLINK switch ports.
You will need a cross-over cable to connect the 2 (however alot of
devices these days auto negotiate crossed cable)
2. Use your netgear as a "b" only WAP (all b\g routers I have seen allow
this. If you broadcast SID then just name it so you can differentiate.
Maybe "Ebin-g" and "Ebin-b"
3. Use the Dlink as your "g" only WAP. Make sure it is at least 3
channels away from your "b" device.
4. Turn DHCP off of the netgear and only run it on the DLINK.
Now everything will work perfectly :)
Also I should note that I run a mixed 802.11 network at my house and I
don't notice any slow down with a G card while B cards are using the
network. I just tested it and was able to pull around 20mbps off my
webserver with the G card while B cards were active.
You should experiment with it because then that would just make thing
even more simple only running one WAP.
best luck
-Chris
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:36:44 EDT