I am unable to see my windows network shares from Linux and they can't see me.

Linux has 2 ethernet cards: eth0 is connected to my wireless broad modem and is working; eth1 is connected to a hub/switch and is assigned 192.168.0.1. This machine is vactor.linux.com aka HumanL. There is a Windows 2000 at 192.168.0.2 known as Nt2k. Occassionally, I have a Windows 95 machine at 192.168.0.7 known as main. The 2 windows machines see each other but not vector, nor can vector see them.

In lookin at SWAT, smbd is running, nmbd and winbindd are not running. (At one time in the past, smbd and winbindd were running.) As I understand, nmbd is reguired for connection to the windows machines but I have yet to be able to start it.

Eventually, this machine is to be the DC and share the internet connection with the other machines some of which will then be upgraded to Linux.

It looks like it's trying to ping your local network from a non-local IP address (i.e. your WAN address). Perhaps your interfaces have switched place. Could you try pinging your local network from eth0 instead to see how the result differs?

ping -I eth0 192.168.0.2

Also, 'ipconfig -a' may provide some useful information in this case. 'route' may also provide useful information.

vector:/~bruce:$ ipconfig -abash: ipconfig: command not foundvector:/~bruce:$ routebash: route: command not foundNote: I used to work as root because of problems like this until MOE-lnx explained that he had no reason to work in root. So, I'm trying to follow his suggestion by working in my user login.

BigPaws:75.94.15.38

What is this address from? The address assigned eth0 by the dhcp of wireless broad band.

I'm not trying to setup ICS until AFTER the intra net is working.

No. I'm hoping, once the intra net is working, to have this machine assign the address of or provide name resolution to the other pcs via DC, DNS, Wins, or whatever. I'll work on that AFTER the intra net is working.

No. Where is it?

What login? plain text or other wise.This is my terminal prompt: vector:/~ bruce:$ and when I'm logged in as root it is: vector:/~ root:#

My guess is that your modem gets an ip from your ISP,then assigns an ipaddress to the internal lan. There is a problem in that doing double NAT can create some other problems some ports.

If not then you are using the modem as a bridge and then using the Vector box to authenticate in some way. You need to know these things in advance.

I hope this is not taken the wrong way. The things you are attempting can have big consequences to your network and possible affect the ISP's network as well. Please take time to read about the proper setup and howtos'. There are protocolsthe you should be aware of. They are tcp/ip, smb, cifs, NAT, port forwarding and iptables.

If you were to say just setup Bind and do improperly you can affect other name servers. The fallout will not be nice.

So. I logged in as root and was able to open SWAT and found the book you referenced. I had started reading it BEFORE I switched to my user account. The examples in the minimal section seemed to indicate that smbd, nmbd, and winbindd were running. But, as I mentioned in my first post, only one of these is running. And I can't find how to start them. (SWAT doesn't have as many buttons (4) as it used to (8 - 10). And status used to allow me to start, stop, or restart all three of these (It didn't work then, either) - BUT NOT ANY MORE!

I read the section on troubleshooting; it seemed to imply that these services, as well as others (such as LDAP) were ALREADY running! And that the intra net connections were working! And I can't even read ANY text in the pictures! Then, I found the following table: Table 5.2. Required OpenLDAP Linux Packages SUSE Linux 8.x SUSE Linux 9.x Red Hat Linux nss_ldap nss_ldap nss_ldap pam_ldap pam_ldap pam_ldap openldap2 openldap2 openldap openldap2-client openldap2-client Vector Linux is neither SUSE nor Red Hat???

Windows can now ping this machine successfully. But now I get an error when I try to refresh Network Places/Entire Network/Microsoft Windows Network/Fowlplay: Fowlplay is not accessible. The account is not authorized to log in from this station(This is a Windows 2000 OS and it is still showing the shares from when this (Linux) machine was running Win98!)

So, I find that my real question is: How to I get eth1 to start at boot time? And the Windows machines are supposed to be able to access the old Windows drive {now hdc1} per smb.config:[public] comment = Public Stuff path = /mnt/win write list = @staff guest ok = Yes fstype = vfat

BTW: For the FIRST time, I see that nmbd is now running but not winbindd

hata_ph: I caught the difference when I reviewed some of my earlier posts trying to get eth0 and eth1 to work, but had forgotten that I had to go into the TUI VASM to start eth1.

Also, When I logged into console from the GUI logon screen, it kept bouncing back to the GUI logon screen but would return to where I was when I selected Console logon. It did that 8 - 10 times while I was writing down the results of VASM/NETWORK/INET/SET.

PS: bigpaws: Oh! I see. AIU, Win9x do not encrypt their passwords. I'll check out that link to Samba-Guide (which I also found in SWAT when logged as root - see above) and ICS, thanks.

ifconfig - see above. Vector is supposed to be the router.

Thanks also for your warning. As it is getting late (for me), I'll check those links first thing in the morning.Yes, my broadband is Clearwire, although I didn't know it was in WA.

Windows can now ping this machine successfully. But now I get an error when I try to refresh Network Places/Entire Network/Microsoft Windows Network/Fowlplay: Fowlplay is not accessible. The account is not authorized to log in from this station(This is a Windows 2000 OS and it is still showing the shares from when this (Linux) machine was running Win98!)

So, I find that my real question is: How to I get eth1 to start at boot time? And the Windows machines are supposed to be able to access the old Windows drive {now hdc1} per smb.config:[public] comment = Public Stuff path = /mnt/win write list = @staff guest ok = Yes fstype = vfat

BTW: For the FIRST time, I see that nmbd is now running but not winbindd

Windows can now ping this machine successfully. But now I get an error when I try to refresh Network Places/Entire Network/Microsoft Windows Network/Fowlplay: Fowlplay is not accessible. The account is not authorized to log in from this station(This is a Windows 2000 OS and it is still showing the shares from when this (Linux) machine was running Win98!)

This is a fault in Wins and smb protocols, not anything in Linux.

Do your host names match? Did you add smb users to the Vector box so that Samba canauthenticate?

Quote

So, I find that my real question is: How to I get eth1 to start at boot time?

OK! I've hooked up the Win95 machine (main), changed the login to Client for Microsoft Windows and added NetBEUI. On restart, I logged in with another user on Vector, was able to open files on Public (/mnt/win - the old 98 disk) but I couldn't do any thing in his home folder. ReLogged with my name: same. I need to tweak smb.config some more. And figure out how to change the policies on the Win 2000 machine (Nt2k) so I can get some files (~2GB) off. Then either figure out how to do a network install of Linux or pull the cover off and temporarily mount a cdrom to install

Linux By Example/quotePrerequisites

This book is not a tutorial on UNIX or Linux administration. UNIX and Linux training is best obtained from books dedicated to the subject. This book assumes that you have at least the basic skill necessary to use these operating systems, and that you can use a basic system editor to edit and configure files. It has been written with the assumption that you have experience with Samba, have read The Official Samba-3 HOWTO and Reference Guide and the Samba-HOWTO-Collection, or that you have familiarity with Microsoft Windows.

If you do not have this experience, you can follow the examples in this book but may find yourself at times intimidated by assumptions made. In this situation, you may need to refer to administrative guides or manuals for your operating system platform to find what is the best method to achieve what the text of this book describes./endquoteI think the Samba Guide would fit this description, also!

Googled Linux administrationThe first item referenced seemed good; looked at fire wall: mentioned two that I've never heard of (in Red Hat ) then proceeds to tell how to set up for 2.4.x with differences for 2.2. AIU we use iptables, both of those use something else. Then in the setup he says such things as 'this relies on the settings in /etc/{somefile} with no indication of how or why to set them. In addition, the description is for a stand-alone pc and again no indication of why to set the options as he does. Let alone, how to find the address needed, such as the isp's name server

The link to ICS assumed that the pcs could already talk to each other.

So far, all of the books (including the ones I have) ignore any mention of any of the difficulties I've had setting up Linux. Vector is the best I've run into in the last 12 - 15 years - I can actually DO something with it without having to learn yet another (seemingly assembly) language just to be able to exit it.