Fwd: Re: [SLE] Configuring a Router
X-pair-Authenticated: 217.235.114.54 From: Nick Selby
Organization: Flyguides.com To: "Stephen P. Molnar, Ph.D." Subject: Re: [SLE] Configuring a Router Date: Wed, 31 Dec 2003 16:21:10 +0100 User-Agent: KMail/1.5.1 X-RCPT-TO: Hi, This will seem rude but it's not - you really need to post this reply to me (thanks for it) to the list itself. The reason is that people use the list archives as learning tools and reference material, so making this a private conversation deprives future users of the benefits of the thread.
So how about resending everything below to the list and then I'll reply there?
FYI, there are separate issues here:
The router seems to be routing so that's actually a SOLVED issue.
The telnet into the MS workstation is a second issue; someone on the list will be able to help with configuring your windows box to allow this.
Having your machines truly networked and each others drives available is another issue, which will involve your sharing the drives on your windows machines, setting up SAMBA on the Linux machine, mapping the network drives on your windows box (to allow your windows machines to see the hard disk of the linux machine) and mounting your windows shared drives on the Linux machine via Samba (which amounts to the same thing as mapping a network drive).
Those last issues are all separate, but rather straightforward. SAMBA has a browser based configuration tool.
So go ahead and re post and I;ll give the same response and add to it, as will other users more expert than me (I have just described most users).
Nick
On Wednesday 31 December 2003 16:13, you wrote:
WOW! Let me say that backwards !WOW
Many, many thanks for your quick reply to my query.
Amazingly simple, at least so far
At 08:52 AM 12/31/2003, you wrote:
On Wednesday 31 December 2003 14:44, Stephen P. Molnar, Ph.D. wrote:
I have just installed a Linksys router on my LAN. As I am functionally illiterate with regard to such things (it took me three days and many hours on the telephone to get my Win2000 box working with the router) what is the simplest way for me to get the linux machine on my LAN to communicate with the router?
Oh yes, I have a DSL connection to the internet.
Should be rather trivial.
1. Plug the router into the wall, into the DSL modem and plug your linux machine into it.
2. I assume you already have the router on speaking terms with your DSL provider; if not you can do it after you get it on speaking terms with the Linux machine.
3. Go into Yast and configure the ethernet device you will use to speak with the router to be DHCP everything - IP, host name, etc. Click okay and let it run suse config
OK, it's at this point that I don't know what I'm doing. I have reconfigured the nic to accept a dynamic IP via DHCP and that seems to work. I can log on to 192.168.1.1/Index.htm and that gets me to the Linksys page via my browser, I assume that is on my router. The routing table shows me that I have local and internet interfaces.
I can ping my Win 2000 box at 192.168.1.100, but when I attempt to telnet in my connection is rejected. LinNeighborhood AddMachine gives me a query error when I attempt to access the machine via that route.
I am totally intimidated by the plethora of choices that yast give me for configuring things - and there lies the continuation of the problem.
4. You should be able now to ping the router; look in the quick set up instructions in the box it came in for the router IP address. Open a browser window and type in the IP address, something like
5. You should now be looking at the router's configuration page. Enter your ISP's user name and password and other information it wants and have the router try connecting. It should be that simple.
HTH!
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Multivariant and stochastic http://www.geocities.com/FoundationForChemistry
-- ---------------------------- Nick Selby
US Mobile: +1 347 804 4410 Germany: +49 89 2737 4527 Germany Fax: +49 89 2737 4529 *Currently in: MUNICH*
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote: <snip>
I have reconfigured the nic to accept a dynamic IP via DHCP and that seems to work. I can log on to 192.168.1.1/Index.htm and that gets me to the Linksys page via my browser, I assume that is on my router. The routing table shows me that I have local and internet interfaces. I can ping my Win 2000 box at 192.168.1.100, but when I attempt to telnet in my connection is rejected. LinNeighborhood AddMachine gives me a query error when I attempt to access the machine via that route. </snip>
Okay, there are three separate issues here. 1. The router setup is SOLVED so I have now changed the thread to SAMBA/W2K Networking Questions 2. Re the "telnet-into-the-MS-workstation;" someone on the list will be able to help with configuring your windows box to allow this. 3. Having your machines on speaking terms an issue involves - creating shares of your drives on the windows machine - Creating a user on the windows machine for your Linux machine - installing (if it's not already installed) and configuring SAMBA - mounting the windows drive from your linux machine/mounting the linux drive on the W2K machine Let's ask the others to help with all these - I need to leave (Happy New Year everyone!!), but I wanted to change the thread subject and set forth the issues so that others can help you. HTH Nick
On Wednesday 31 December 2003 18:04, Nick Selby wrote:
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote: <snip> 2. Re the "telnet-into-the-MS-workstation;" someone on the list will be able to help with configuring your windows box to allow this.
3. Having your machines on speaking terms an issue involves
- creating shares of your drives on the windows machine - Creating a user on the windows machine for your Linux machine - installing (if it's not already installed) and configuring SAMBA - mounting the windows drive from your linux machine/mounting the linux drive on the W2K machine </snip>
What happens when you open a browser window and try to surf to http://localhost:901 ? -- ---------------------------- Nick Selby US Mobile: +1 347 804 4410 Germany: +49 89 2737 4527 Germany Fax: +49 89 2737 4529 *Currently in: MUNICH*
At 07:03 AM 1/1/2004, you wrote:
On Wednesday 31 December 2003 18:04, Nick Selby wrote:
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote: <snip> 2. Re the "telnet-into-the-MS-workstation;" someone on the list will be able to help with configuring your windows box to allow this.
3. Having your machines on speaking terms an issue involves
- creating shares of your drives on the windows machine - Creating a user on the windows machine for your Linux machine - installing (if it's not already installed) and configuring SAMBA - mounting the windows drive from your linux machine/mounting the linux drive on the W2K machine </snip>
What happens when you open a browser window and try to surf to
Could not connect
?
-- ---------------------------- Nick Selby
US Mobile: +1 347 804 4410 Germany: +49 89 2737 4527 Germany Fax: +49 89 2737 4529 *Currently in: MUNICH*
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 01 January 2004 13:31, Stephen P. Molnar, Ph.D. wrote:
At 07:03 AM 1/1/2004, you wrote:
On Wednesday 31 December 2003 18:04, Nick Selby wrote:
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote:
<snip>
2. Re the "telnet-into-the-MS-workstation;" someone on the list will be able to help with configuring your windows box to allow this.
3. Having your machines on speaking terms an issue involves
- creating shares of your drives on the windows machine - Creating a user on the windows machine for your Linux machine - installing (if it's not already installed) and configuring SAMBA - mounting the windows drive from your linux machine/mounting the linux drive on the W2K machine
</snip>
What happens when you open a browser window and try to surf to
Could not connect
?
BTW, Stephen, you needn't (shouldn't) cc me and the list - means I get two copies, which is unnecessary. ***I'm still rather incompetent and would ask others on the list to review what I am saying here and chime in where I am wrong, and to take this to the next level!*** What I would do would be this: First make sure that SAMBA is actually installed. do rpm -q samba and see if you get something like nick@linux:~> rpm -q samba samba-2.2.7a-72 And while you're at it, see if apache is installed, too. If not, then go into Yast and have your Suse disks ready to go and install Samba. If it is installed, see if samba is running: Yast -> System -> Runlevel Editor -> Runlevel properties DON'T CHANGE ANYTHING IN HERE YET. Just scroll down until you see smb (it's alphabetical) and see if it's running. If not, make it run. Try browsing to localhost:901 again. If you get "could not connect," or some such complaint, surf to 127.0.0.1 and see what happens (you may just see "index of /" - that would be good and mean that apache is running.) If that doesn't work ping localhost or ping 127.0.0.1 If nothing comes back, find out if apache is even installed: rpm -q apache and you should get something like nick@linux:~> rpm -q apache apache-1.3.27-82 If not, install it. You can start apache by doing /etc/init.d/apache start Then open a browser window and try all this again and let us know what happens. Folks, I'm getting out of my depth can others chime in here? Thanks! Nick
At 07:48 AM 1/1/2004, you wrote:
On Thursday 01 January 2004 13:31, Stephen P. Molnar, Ph.D. wrote:
At 07:03 AM 1/1/2004, you wrote:
On Wednesday 31 December 2003 18:04, Nick Selby wrote:
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote:
<snip>
2. Re the "telnet-into-the-MS-workstation;" someone on the list will be able to help with configuring your windows box to allow this.
3. Having your machines on speaking terms an issue involves
- creating shares of your drives on the windows machine - Creating a user on the windows machine for your Linux machine - installing (if it's not already installed) and configuring SAMBA - mounting the windows drive from your linux machine/mounting the linux drive on the W2K machine
</snip>
What happens when you open a browser window and try to surf to
Could not connect
?
***I'm still rather incompetent and would ask others on the list to review what I am saying here and chime in where I am wrong, and to take this to the next level!***
What I would do would be this:
First make sure that SAMBA is actually installed. do
rpm -q samba
and see if you get something like
nick@linux:~> rpm -q samba samba-2.2.7a-72
And while you're at it, see if apache is installed, too.
If not, then go into Yast and have your Suse disks ready to go and install Samba. If it is installed, see if samba is running:
Yast -> System -> Runlevel Editor -> Runlevel properties
DON'T CHANGE ANYTHING IN HERE YET. Just scroll down until you see smb (it's alphabetical) and see if it's running. If not, make it run.
Try browsing to localhost:901 again. If you get "could not connect," or some such complaint, surf to 127.0.0.1 and see what happens (you may just see "index of /" - that would be good and mean that apache is running.)
Both applications are installed and running. I should note that I had a functional LAN before I replaced the hub with the router. Here is my current arrangement: Machine IP Igor 192.168.1.100 AbNormal 192.168.1.101 (this box is the Linux box, both other machines dual boot; Linux and win2000) Inga 192.168.1.102 (as a mad scientist, myself, I consider Young Frankenstein to be a classic movie) Now, each machine can ping both of the others. As I am inherently lazy and don't understand networking I use LinNeighborhood to connect the linux box to the Win2000 boxes. I just tried to access Inga from AbNormal, via LinNeighborhood, and it worked. However, when I attempt the same thing, LinNeighborhood AbNormal to Igor, I get: GetSMBShare:smbclient -L igor -I 192.168.1.100 -Uadministrator%***** -W ffc -d3 -p 139 Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" added interface ip=192.168.1.101 bcast=192.168.1.255 nmask=255.255.255.0 Client started (version 2.2.8a-SuSE). Connecting to 192.168.1.100 at port 139 Domain=[FFC] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_BAD_NETWORK_NAME ipconfig/all on Igor gives me: Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : igor Primary DNS Suffix . . . . . . . : ffc Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : ffc Ethernet adapter Local Area Connection 4: Media State . . . . . . . . . . . : Cable Disconnected Description . . . . . . . . . . . : Efficient Networks Enternet P.P.P.o.E Adapter #2 Physical Address. . . . . . . . . : 44-45-53-54-77-77 Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ffc Description . . . . . . . . . . . : NETGEAR FA311 Fast Ethernet PCI Adapter Physical Address. . . . . . . . . : 00-A0-CC-E1-4F-25 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 67.36.13.26 66.73.20.40 Lease Obtained. . . . . . . . . . : Thursday, January 01, 2004 5:08:40 AM Lease Expires . . . . . . . . . . : Friday, January 02, 2004 5:08:40 AM Finally, when I attempt to access the web, via browser, AbNormal tells me 'couldn't access remote server.'
If that doesn't work ping localhost or ping 127.0.0.1
If nothing comes back, find out if apache is even installed:
rpm -q apache
and you should get something like
nick@linux:~> rpm -q apache apache-1.3.27-82
If not, install it. You can start apache by doing
/etc/init.d/apache start
Then open a browser window and try all this again and let us know what happens. Folks, I'm getting out of my depth can others chime in here?
Thanks! Nick
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 31 December 2003 17:35, Stephen P. Molnar, Ph.D. wrote: <snip>
WOW! Let me say that backwards !WOW
Many, many thanks for your quick reply to my query.
Amazingly simple, at least so far
At 08:52 AM 12/31/2003, you wrote:
On Wednesday 31 December 2003 14:44, Stephen P. Molnar, Ph.D. wrote:
I have just installed a Linksys router on my LAN. As I am functionally illiterate with regard to such things (it took me three days and many hours on the telephone to get my Win2000 box working with the router) what is the simplest way for me to get the linux machine on my LAN to communicate with the router?
Oh yes, I have a DSL connection to the internet.
Should be rather trivial.
1. Plug the router into the wall, into the DSL modem and plug your linux machine into it.
2. I assume you already have the router on speaking terms with your DSL provider; if not you can do it after you get it on speaking terms with the Linux machine.
3. Go into Yast and configure the ethernet device you will use to speak with the router to be DHCP everything - IP, host name, etc. Click okay and let it run suse config
OK, it's at this point that I don't know what I'm doing. I have reconfigured the nic to accept a dynamic IP via DHCP and that seems to work. I can log on to 192.168.1.1/Index.htm and that gets me to the Linksys page via my browser, I assume that is on my router. The routing table shows me that I have local and internet interfaces. </snip>
Since the first question was solved I posted this as SOLVED and changed the thread to address two other issues you brought up. Happy New Year! Nikc
participants (3)
-
Nick Selby
-
Stephen P. Molnar, Ph.D.
-
Stephen P. Molnar, Ph.D.