Setting up remote boot nodes help!!

[rsbriggs]

I end up booting each one twice when I first bring them up. Once, and I tail /var/log/messages to find their MAC address, edit dhcpd.conf and lts.conf, then reboot and watch var/log/messages again to make certain that they connected.

Do you have a simple way to set up a Samba share, PCZ? I'm not concerned about security on the farm sub-net - there are two sets of NAT translations and 3 separate firewalls between them and the internet.

But, I'll tell you what, setting up ZoneAlert on my Windows DSL router box was certainly eye-opening. I think someone must have been running a porn server or something on my system, given the number of hits (now starting to dwindle down) I was getting on port 80, and that is supposed to be AFTER the USWest NAT firewall.

Also, after contacting the Mandrake Linux site, I'm getting hits on port 6881 from ezoffice.mandrakesoft.com about once per second. Wonder what THAT is all about?

The M7VIQ boards are quite easy to deal with. My only concern about the boards is that there are some electrolytic caps on the board that are running at close to 200 degrees F. - somewhat over their spec'ed temperature rating. The caps run much hotter than the processor or either of the bridges....

[magnav0x]

Download samba and install it. Of course this will all depend on what distro you are using. I use gentoo, so all I do is 'emerge samba'. You guys may be able to use RPM's or may be forced to download the source, build and install it. Replace your smb.conf with this and of course edit it to share the directory of your choosing. For example, I made the user 'pcguest' with a password of null and put all the stuff I wanted to share out (like my df client for monitoring from my windows box). This will work right away, assuming you have the 'pcguest' user on your box with no password. After you have replaced the smb.conf with this just issue the 'smbd -D' command to start the samba daemon. Good luck, hope it helps.

[global]
workgroup = workgroup
server string = none
interfaces = 192.168.1.1/64 (variable)
security = SHARE
encrypt passwords = YES
password level = 2
username level = 2
log file = /var/samba
max log size = 50 (default)
lock dir = /lock
guest account = pcguest
[tmp]
comment = (your coments here)
path = /usr/tmp
read only = No
directory mask = 0775
guest ok = yes
browseable = no

[homes]
comment = Home Directories
browseable = no
read only = no
create mode = 0750

[printers]
comment = All Printers
browseable = no
printable = yes
public = no
writable = no
create mode = 0700

[Gentoo Samba]
comment = pcguest
path = /home/pcguest
public = yes
writable = yes
printable = no
write list = @staff

[rsbriggs]

Gave it a try, but ended up with the "usual" result - can't see the share from any Windows boxen. Never have been able to get Windows boxes to see Linux boxes successfully on this network. I'd LOVE to be able to do it, since Textpad on Windows is my preferred editor in any and all situations.

[Dyyryath]

Samba's pretty simple, I use it extensively both at work and at home.

Couple of questions (which may have already been answered farther up, but I'm feeling lazy ):

(1) Are you using a domain controller or are your machines peer to peer?

(2) What's the domain name/workgroup name you're using? If you're using a domain, what's the PDC's name?

(3) Are they all on the same subnet?

(4) What distro are you using?

(5) What version of Windows are your other boxes using?

Given these, I can set you up a config that will work fine.

[IronBits]

1) peer to peer
2) dbestern
3) yes - LAN side
4) Madrake 9.1
5) XP or w2k

Is it done yet? (over here on ether silly)

[rsbriggs]

1) peer to peer
2) MSHOME
3) no, but that isn't the problem. The ONE important machine is dual homed
4) Red Hat 9.x
5) XP-Pro

[magnav0x]

rsbriggs, I can't "see" my linux boxes either. But if you goto start->run and type \\192.168.1.102 or whatever the IP for the linux box is, it SHOULD connect.

[rsbriggs]

\\192.168.0.2
The network path was not found

ping 192.168.0.2
no problem

[the-mk]

Originally posted by rsbriggs
\\192.168.0.2
The network path was not found

ping 192.168.0.2
no problem

is there a firewall blocking port #139?

[rsbriggs]

Nope - it's on the same subnet. I read the samba man page for a while, and tweaked. Still can't get NMBD to run for some reason, so can't "see" the computer, but a \\IP direct connect and some tweaks results in this DCMonitor output:

CN Computer name Struct Gen Next gen Buff gens Best energy Status 
4  Kathey          0      0     0       0       0.000       Unknown 09:45 31/08 
1  Dell4600-1      0      0     0       0       0.000       Unknown 09:45 31/08 
12 Barton-1       21     54    29       1       6.190       Running 
6  OldAMD         41     62     9       1       5.651       Running 
2  Dim4500         6    106    44       0       5.864       Running 
5  Dell600SC      11    126    39       0       6.282       Running 
3  Dell4600-2     31    138    19       1       4.511       Running 
13 Linux DF-1      1    184    49       0       10000000.000       Running 
14 Linux DF-2     16    153    34       1       4.875       Running 
15 Ws002           6     33    44       1       6.418       Running 
16 ws003          21    244    29       1       4.046       Running 
17 ws004          26    208    24       1       4.065       Running 
18 ws005           6    130    44       0       4.096       Running

(dunno where computer # 7, 8, 9 or 10 are )

[PCZ]

rsbriggs

When you installed red hat you basically did a custom install and selected everything
Based on this assumption you will have the same tools as me installed.

Creating an SMB share on the red hat server takes a few seconds only and you dont have to touch smb.conf

You already have windows PC's in either a workgroup or domain.

Your windows PC's log on with a usermame and password. the password might be blank but it is still a password



from the start menu in KDE/Gnome select System Settings , Server Settings , Samba Server.

A little applet will load called Samba Server Configuration.

1:From the Preferences menu select Server settings
Type the name of your workgroup or the netbios name of your domain in the workgroup box

click on the security tab and make sure Authentication mode is set to User
Click OK.

3: From the Preferences menu select Samba Users.
click on the add user button.
The Create New Samba User dialog box will pop up.
click on the drop down to the right of Unix Username and select root from the menu.
fill in the windows username and password boxes.
click ok. and ok again

4:
Click on the green add button
The Create Samba Share dialog box will pop up

Browse to the directory you want to share.
Type a description if you want.

Change the setting of Basic Permissions to Read /Write

Click on the Access button
it should have Only allow access to specific users selected
pick a tick in the box called root
click ok

select File Quit

the config will be saved and Samba restared automatically.

Note: This config is only for use in a secure enviroment.

[rsbriggs]

Unfortunately, I made the mistake of installing Ximian Evolution, which has me trapped inside a Gnome login, and seems to restrict me from MANY selections I had available before installing it. Let me re-try a log-on as root instead of as a normal user.

EDIT:

Nope. Anyone know how I can get back to my nice KDE desktop? I can't find where a display manager is being set in Red Hat...

DCMonitor needs a column for "structures changed" on a computer by computer basis, rather than just totalling it....

[PCZ]

I think the html that it outputs could be fed into a stats system.
Over to someone else to work that one out.

[IronBits]

www.dbestern.com/dcmonitor.htm
Dyyryath is busy working some of his magic

[PCZ]

so how do you get the best energy and status in the web output

[AMD_is_logical]

I've used Biostar M7VIT pro motherboards in a diskless cluster (with mii.o and via-rhine.o drivers). They don't have onboard video, but there is a "Halt on no errors" option that lets them run without a video card (once they're set up). They can run fsb=333MHz. There's no power-on after power-fail option (that I could find), so I've been putting a 100uF cap where the power-on switch would normally go. That causes it to turn on when the power goes on.

[IronBits]

Originally posted by PCZ
so how do you get the best energy and status in the web output

I dunno, I'm using your suggestion of a Samba share and DCmonitor.

[IronBits]

Originally posted by AMD_is_logical
There's no power-on after power-fail option (that I could find), so I've been putting a 100uF cap where the power-on switch would normally go. That causes it to turn on when the power goes on.

Nice! Where are the docs and pics of course?

[PCZ]

Sorted
I was using version 0.7
version 0.72 has the extra info

[IronBits]

Funny how a little thing like a .02 can make
Glad you got it running.
I moved em all over to pxe nodes, lost one in the shuffle...
Might be a little bead of sweat that got on it, so will let it dry out and try again in a few hours.
/me shrugs
Glad that's over with

[PCZ]

I bet you know a lot more about linux now ?

I found it quite a steep learning curve but well worth it.

[IronBits]

Well... I know a lot more about pxe for sure.
Thanks to you, rsbriggs and Dyyryath

[AMD_is_logical]

Originally posted by IronBits
Nice! Where are the docs and pics of course?

You want a pic of the cap?

[IronBits]

Nice pic!
That's all it takes to get a motherboard to boot up if it doesn't support power on when electricity is restored?!
I like it

[Paratima]

Schweet!

[AMD_is_logical]

Originally posted by IronBits
That's all it takes to get a motherboard to boot up if it doesn't support power on when electricity is restored?!
I like it

I've only tried it with Biostar M7VIT pro motherboards, but it works great with them.