On Tuesday 16 April 2002 13:22, jaakko tamminen wrote: - Maybe a stupid question as I have not followed the thread, but have You any - firewall running? - - My setup looks like Yours, and it works, and I don't have any firewall - running on my workstation. Not stupid, quite relevant. I forgot to mention this to the new participants in this thread. I have no firewall running on SuSE 7.3. On the Win 98 SE machines, I have Norton Personal Firewall setup on all three. Unfortunately, Norton PF for Win is quite different in its fomat than for Mac, which is what I am most familiar with. As I have no problems in Win 2k and I do not make changes on the other computers when I boot into SuSE ;-) I can only assume that there either is a general SuSE networking setup problem that I am experiencing, or it most likely has something to do with ping and smbclien not being able to penetrate Norton PF. Unfortunately, I don't know how to reconfigure the Win version properly. Cheers, Brian

On Tuesday 16 April 2002 15:17, Peter Lewis wrote: - Have you tried a ping from win98 machine to another win98 machine? If that - works I think that you can eliminate the Norton PF blocking at the win98 end - and concentrate on the routing from SuSE to win98. Everything with Win works fine, I.e.: Win 2k -> Win 98 SE, Win 98 SE -> Win 98 SE, Win 98 SE -> Win 2k. Only SuSE -> Win 98 SE doesn't work. I just don't know how to find out what is wrong at the SuSE end. Totally baffled, Brian -- Is Windows the best desktop system because it is used by a majority of computer users, or is it simply the desktop system installed on a majority of computers? Choose freedom. Choose Linux.

On Tuesday 16 April 2002 15:55, Peter Lewis wrote: - Can you ping the SuSE machine from the win98 and win2k machines? - Umm, I am not sure how to do this from Win, just run -> ping IP address? Please note that while all machines on the network are PCs, I am a former Mac user and it is there that my strengths lie. Also, note that SuSE is part of a dual boot with Win 2k, you mention SuSE and Win 2k as if they were on separate machines. - - What are the IP addresses assigned to all hosts (and routers if used) and - what are the netmasks? - The LinkSys router is 192.168.1.1 Netmask is 255.255.255.0 No static (?) IP addresses here, but I believe SuSE is always 192.168.1.101 The others are 102, 103 and 104. It seems to simply depend on which router port the various machines are connected to. - - You obviously have internet connection, which host provides that or is it - through a router box? - 3 Com cable modem and LinkSys router. - - Can you reach the internet from the SuSE machine? - Doin it 99.9% of the time. I actually only use Win like most on the list, to run a specific program or two that isn't available with SuSE. - Do you have a DNS on the network? - Loaded question ;-) I really don't know. I have had discussions on the list about this, because I have been trying to equate "computer name" and "workgroup" in the Win world to something in SuSE. I do know that I have tried to equate "thor" as "computer name" or "host" in SuSE and "asgaard" with workgroup" or "host domain", if this helps. - - Are you pinging by ip number of machine name? - I'm pinging by IP. - - (End of third degree for the moment :-) Whew, Brian

On Tuesday 16 April 2002 18:51, Peter Lewis wrote: - there is a ping in win98 (C:\windows\ping.exe) and it can be run from a - dos-box with the target host's ip address. For example: - - ping 192.168.1.101 - OK, the ping timed out when I tried from one of the Win 98 SE machines. Just got to thinking, how do I check my IP address from SuSE on my SuSE computer? - - I am not conversant with the LinkSys router, does it have a dhcp server? Do - the hosts (SuSE and win98) fetch their ip address from a dhcp server? - Well, the specs in my manual state that the protocol used is CSMA/CD. This doesn't tell me much. From the web info at http://www.linksys.com it looks as if my model (BEFSR41 v.2) supports DHCP and (?) DNS for sure, but the info appears to be mainly limited to reviews or troubleshooting. I hope this helps provide some background info that can help to localize the problem. Cheers, Brian

On Tuesday 16 April 2002 20:12, Peter Lewis wrote: - As root type in the command: - - ifconfig -a - - Then as any user type in the commands - - netstat -tn - netstat -rn - - See what you get. OK, that makes a difference: ifconfig -a eth0 Link encap:Ethernet HWaddr 00:50:2C:01:2B:1B inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:2cff:fe01:2b1b/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 RX packets:175124 errors:0 dropped:0 overruns:0 frame:0 TX packets:193281 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:129379728 (123.3 Mb) TX bytes:56967625 (54.3 Mb) Interrupt:11 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:160 errors:0 dropped:0 overruns:0 frame:0 TX packets:160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10432 (10.1 Kb) TX bytes:10432 (10.1 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) # netstat -tn Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 192.168.1.100:37755 66.57.9.47:6346 ESTABLISHED tcp 0 5514 192.168.1.100:37748 80.62.224.89:6346 ESTABLISHED tcp 0 0 192.168.1.100:32774 65.119.4.104:143 ESTABLISHED tcp 0 1596 192.168.1.100:37517 80.0.194.171:6441 ESTABLISHED tcp 0 1295 192.168.1.100:37426 24.197.250.5:6346 ESTABLISHED tcp 0 522 192.168.1.100:37782 68.81.42.27:6346 ESTABLISHED tcp 0 1304 192.168.1.100:37815 24.49.156.5:6347 ESTABLISHED # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0 eth0 So the SuSE IP address for my machine is 192.168.1.100 (may be the same in Win 2k). I pinged from a Win 98 SE machine and was successfull. Now we are getting somewhere ;-) The question is what does this than say about the condition of the SuSE network, i.e. why can't I get smbclient and LinNeighborhood to work? Cheers, Brian

On Tuesday 16 April 2002 1:35 pm, you wrote:

Now we are getting somewhere ;-) The question is what does this than say about the condition of the SuSE network, i.e. why can't I get smbclient and LinNeighborhood to work?

Well, I always found Windows networking to be wild and wacky. When it works, it really is very good, but too often it doesn't work, and it isn't immediately obvious what the problem is. So it's difficult to know whether your problem is with Windows itself, or with the Linux layer you're trying to lay on top of that. Firstly, are you sure you have installed Samba (including smbclient?). Do rpm -qa | grep samba to find out. Second, is the smbfs module loaded. Find out by doing lsmod If it is not, (as root) do modprobe smbfs to load it. I think you need to add a line to /etc/init.d/boot.local to do this automatically at boot, but others here will be more knowledgeable on this. Thirdly, make smbmnt and smbumount suid root, so that ordinary users can use them. As root, do chmod 4755 /usr/bin/smbmnt chmod 4755 /usr/bin/smbumount I am sure there are some security implications in this (which others may perhaps be kind enough to point out), but it may be sensible to get the thing working first and then worry about them. (Thanks to Nick Davis for these two points: http://www.linuxworld.com/site-stories/2002/0318.linuxcorp-p2.html) Fourthly, ensure that there are shared resources on the Windows (I am assuming 98) machines. You may have done this already, but if you have not, you need to add the File Sharing for MS Networks service via right-click/Properties/Add on the Network Neighbourhood icon. Ensure that all Win PCs are in the same workgroup, and that the name (Identification tab) is proper (ie no weird characters like periods). Then, via the My Computer icon, right-click the resource you want to share (eg C:), and select Sharing. Give it a name and description, and decide on whether you want to give full or read-only access. Fifthly, try pinging from each computer to all others. If this does not work, there is something wrong at a base level, and nothing else will work. Ensure that all Win PCs can see the shared resources of all others - if this does not work, there is something wrong with your Windows setup, which will need to be sorted out before you try browsing via Samba. Now, open LinNeighbourhood. Click on Options/Browse entire network. In the popup box, you should be the user (greyed out). (If you are not, tick the Browse as user box, and enter your username and password. Then untick the box.) Click on OK. Give it a few seconds, particularly if you have just made changes to your Win PCs - it can take up to 10 minutes for changes made to a Win network to propagate. But you should eventually end up with a nested hierarchy in the left-hand panel, with your machine at the top. Below it there is a network (perhaps called TUX-NET) which will have entries for the Linux machines on which Samba is installed (so your machine should also appear here). Below that there is another network (perhaps called WORKGROUP). This should consist of your Windows PCs. If it does not, try doubleclicking on the entry. Each PC entry should have a + next to it, and if you click on that you should see the shares you established earlier. Doubleclick on one, click Mount, and LN should mount it at your chosen point, and open Konq to display it. HTH Kevin

On Suse 7.1 you do /home/gringo/ /etc/rc.d/smb status Checking for service smb: OK OK root@gringo Wed Apr 17 03:01:17pm /home/gringo/ Brian Marr My suggestion -bypass the switch and connect directly to a Win PC. Do start > run > ping xxxx or start > run > ping (computer name) On Wednesday 17 April 2002 12:28, you wrote:

On Tuesday 16 April 2002 23:23, Kevin Donnelly wrote: - Firstly, are you sure you have installed Samba (including smbclient?).  Do - rpm -qa | grep samba - to find out. - Only smbclient is installed. I saw no reason to install the whole package as the rest of my family are more novices than even I am ;-) - - Second, is the smbfs module loaded.  Find out by doing - lsmod - If it is not, (as root) do - modprobe smbfs - to load it.  I think you need to add a line to - /etc/init.d/boot.local - to do this automatically at boot, but others here will be more knowledgeable - on this. - No, the smbfs module was not loaded. can anyone on the list confirm these instructions, maybe with a little more detail? I don't want to end up not being able to boot my system ;-) - - Thirdly, make smbmnt and smbumount suid root, so that ordinary users can use - them.  As root, do - chmod 4755 /usr/bin/smbmnt - chmod 4755 /usr/bin/smbumount - I am sure there are some security implications in this (which others may - perhaps be kind enough to point out), but it may be sensible to get the thing - working first and then worry about them. - I am again not sure I want to do this (as per installing all of SAMBA) but am willing to consider it on advice from the list.

Cheers,

Brian

On Thursday 18 April 2002 9:56 am, Brian Durant wrote:

- Now, open LinNeighbourhood.  Click on Options/Browse entire network.  In - the - popup box, you should be the user (greyed out).  (If you are not, tick - the - Browse as user box, and enter your username and password.  Then untick - the - box.)  Click on OK. - Doesn't work for some reason. I have to press the add button and add manualy. It doesn't show up in LinNeighborhood, but I can navigate to an empty folder in Konq (/home/usr/mnt/<host>/<shared resource> Isn't there a way that I can get these drives to mount on my desktop as a drive without having to do LinNeighborhood, manually adding the shared resource and then using Konq to navigate (at startup)? I would like it to work the way my Win 2k partition just pops onto my desktop at startup. I see that LN has an "-m" command in the command line, but I am not sure how to go about this. I also see in the read me file that LN can't mount printer shares. Hmm.

Are you giving LN enough time, and double-clicking on the WORKGROUP name? sometimes it can take half a minute to find the shares. Having them pop on to the desktop in Windows is nothing - I presume that's just read from a config file somewhere. When you click on them in Windows, it has to go looking for them too. Others here may know more about it than me, but I would have thought it might be possible to use smbmnt in your boot.local file, or even smbclient in fstab. If I were you, I would get it all working first, and then start refining it - this goes for the printer shares too.

Any ideas how I can print to a shared printer? YAST2 can't seem to find either of the HP printers on the LAN :-(

It is possible to use CUPS to print to a shared Windows printer, but although I keep meaning to try it, I've never done it. Perhaps someone else here can give you a few pointers. Kevin

Are you pinging computer names or computer ip address ? Brian Marr On Tuesday 16 April 2002 18:01, you wrote:

On Tuesday 16 April 2002 15:17, Peter Lewis wrote: - Have you tried a ping from win98 machine to another win98 machine? If that - works I think that you can eliminate the Norton PF blocking at the win98 end - and concentrate on the routing from SuSE to win98.

Everything with Win works fine, I.e.: Win 2k -> Win 98 SE, Win 98 SE -> Win 98 SE, Win 98 SE -> Win 2k. Only SuSE -> Win 98 SE doesn't work. I just don't know how to find out what is wrong at the SuSE end.

Totally baffled,

Brian

Maybe just connect your Linux box to a single Win PC and attempt to ping between the two. Brian Marr On Tuesday 16 April 2002 18:16, you wrote:

On Tuesday 16 April 2002 16:42, Brian Marr wrote: - Are you pinging computer names or computer ip address ?

IP addresses.

Cheers,

Brian