[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] setting up a standalone lab with a wireless router



I was able to try some things over the weekend and have the router
working with a standalone k12ltsp server. I'll work with it and pass on
anything I discover that seems worth passing on.

Gary

On Wed, 2005-04-27 at 22:57 +0200, Gustav J Kramer wrote:
> Gary,
> 
> I'm trying to envision your set up in order to figure out what's going
> on but I'm getting lost somewhere.  What is the difference in
> configuration between:
> 
> "The router works if I connect it to the DSL modem. The wireless
> computers can see the server etc. (and everyone can see a smb share we
> have on one of the machines)"
> 
> and
> 
> "I connect a Windows XP computer via wireless and it can see the outside
> world when the outside world is plugged in but can not see the
> server...It can!!! see another Windows XP computer on the same wireless
> connection."
> 
> If all you did was move the cable coming from the MODEM from the
> Internet port on the router to eth1 on the Terminal Server then all that
> should have happened is that you should have lost your internet access
> from all machines as they would no longer be routed correctly (they
> would still have the router as the gateway vice the terminal server).
> Something is missing here!
> 
> - gustav
> 
> > On Wed, 2005-27-04 at 14:04 -0500, Gary Frederick wrote:
> > Thanks for the help Gustav. Perhaps you gave me some of the answer.
> > 
> > I'll say more.
> > 
> > I have a k12ltsp server. It has two nics and the usual k12ltsp setup.
> > One can connect to a DSL modem (eth1) and the other to the router
> > (eth0). I have a wireless router (Netgear wgt624 v2).
> > 
> > The router works if I connect it to the DSL modem. The wireless
> > computers can see the server etc. (and everyone can see a smb share we
> > have on one of the machines)
> > 
> > 
> > I am testing the k12ltsp server with the internet side unplugged and the
> > router connected to the other card (eth0).
> > 
> > I connect a diskless client via ethernet cable to the router and it
> > works. It can do the usual client thing.
> > 
> > I connect a Windows XP computer via wireless and it can see the outside
> > world when the outside world is plugged in but can not see the server. I
> > tried pinging both the eth1 and eth0 address for the server and it can
> > not see them. It can!!! see another Windows XP computer on the same
> > wireless connection.
> > 
> > If I take out the wireless card and connect the Windows XP computer via
> > ethernet cable it can see the server but now can not see the other XP
> > computer that is on wireless.
> > 
> > Your comment "...on the router (which has DHCP disabled)" got me
> > thinking. The router does NOT have DHCP disabled. I'll try disabling
> > that tomorrow and see if it helps.
> > 
> > SAMBA is an exercise for another day :-) I just want the wireless
> > computers to be able to ping the router.
> > 
> > ...
> > 
> > 
> > ...
> > 
> > I do not know a lot of system admin. I'm learning in my spare time, but
> > it is slow. Now I guess I am learning more about how k12ltsp uses DNS
> > and DHCP :-) 
> > 
> > Gary
> > 
> > 
> > On Wed, 2005-04-27 at 19:33 +0200, Gustav J Kramer wrote:
> > > Gary,
> > > 
> > > There are others on the list far more capable but I will try and get you
> > > started until they can chime in:
> > > 
> > > I'm assuming that when you say the clients cant see the server you mean
> > > they can't connect via a windows (smb) share not that they cant ping the
> > > server?
> > > 
> > > For the wireless XP clients they will have to belong to the same domain
> > > or workgroup as the server. Given the size of your lab I would guess
> > > Workgroup.  You can check it by right clicking on "My Computer", then
> > > left clicking on "Properties" and again on the "Computer Name" tab.
> > > 
> > > You can confirm the Domain/Workgroup (and that the SAMBA servers are
> > > running) from within WEBMIN.  Click on the "Servers" button, then "Samba
> > > Windows File Sharing",(from here you can see whether the servers are
> > > running) then on "Windows Networking".
> > > 
> > > With respect to the wired clients, If they are thin clients and they
> > > boot to a graphic log on prompt then they are connected, the server
> > > appears as a local device.  If they are standalone linux boxes then they
> > > will only "see" the server if you connect via NFS or through a Windows
> > > share, again on the same workgroup or domain.  If the wired clients are
> > > windows clients, then like the wireless clients, you will have to
> > > confirm that they belong to the same workgroup or domain.
> > > 
> > > I'm a bit confused when you say that you connect the server to the
> > > internet.  Is the server configured with two NICs, one wired to the
> > > internet and the other to one of the four LAN ports on the router (which
> > > has DHCP disabled)?
> > > 
> > > 
> > > I hope this helps,
> > > 
> > > - gustav
> > > 
> > > On Wed, 2005-27-04 at 07:30 -0500, Gary Frederick wrote:
> > > > Howdy
> > > > 
> > > > I am trying to set up a standalone lab, one that is not connected to the
> > > > internet. It has a k12ltsp server and a Netgear wgt624 v2 wireless
> > > > router and 4 clients.
> > > > 
> > > > I have two clients connected to the router via ethernet cable and two
> > > > connecting via wireless. The wireless clients are running XP.
> > > > 
> > > > The two clients connected to the router via ethernet cable can talk to
> > > > each other.
> > > > 
> > > > The two connected via wireless can talk to each other.
> > > > 
> > > > The wired clients can not see the wireless clients and vice versa.
> > > > 
> > > > None of the clients can see the server.
> > > > 
> > > > and when I connect the server to the internet, all 4 clients can see the
> > > > outside world (but still will not talk to the server or across the
> > > > wire/wireless connection.
> > > > 
> > > > What am I doing wrong?
> > > > 
> > > > Gary
> > > > 
> > > > This is a recent k12ltsp setup. The XP clients are current.
> > > > 
> > > > _______________________________________________
> > > > K12OSN mailing list
> > > > K12OSN redhat com
> > > > https://www.redhat.com/mailman/listinfo/k12osn
> > > > For more info see <http://www.k12os.org>
> > > 
> > > _______________________________________________
> > > K12OSN mailing list
> > > K12OSN redhat com
> > > https://www.redhat.com/mailman/listinfo/k12osn
> > > For more info see <http://www.k12os.org>
> > 
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN redhat com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]