Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Saturn2888

Pages: 1 ... 32 33 [34] 35 36
496
Installation and Upgrades / Re: Thin Client
« on: April 04, 2009, 07:00:21 am »
I haven't even gotten the Thin net server to save changes. It keeps giving me that error looking for a boot image. I tried copying the contents of the DVD in there and that didn't work either.

But that's a good tip provided I can get this working even. I actually just wanna use it to install RedHat into another machine w/o a CD drive and only 1.1 USB (so I can't use that).

497
Installation and Upgrades / Thin Net / PXE boot
« on: April 04, 2009, 04:10:07 am »
I'm wondering about the error eBox gives when trying to configure a Thin Net. Since the documentation shows nothing about it, I've been asking around for the last week trying to figure something out and no one knows.

The error I get is: "You need to upload a boot image to eBox if you set it as next server"

I've looked. What is a boot image?

498
The ISO install was fast and speedy for me. If not, I wouldn't have been able to reconfigure the OS 5 times by hand in a day.

499
Yeah, saw that. It did NOT make sense until after I looked around and found it. Apparently it got released as I got involved in the eBox community. I should've gone back and deleted my post. Aw well.

500
Installation and Upgrades / Re: Load Balancing and Fail-over
« on: April 01, 2009, 10:52:45 pm »
Nothing, don't worry about it. I was talking it over with a friend. I was thinking if someone had fiber to the house because I might be getting that in 6 months. Since I dunno how that works specifically, I thought I'd ask later.

501
Installation and Upgrades / Re: Load Balancing and Fail-over
« on: March 31, 2009, 08:32:48 pm »
And because this brings up a good point, does load balancing happen if there are two NICs using the same Gateway address? I thought I saw it doing this but I don't remember. All of my IPs go to the same physical modem, but I was just wondering.

502
It's gonna ask for a user/pass, there is no current implementation of a Guest account with eBox so far that I've seen.

This is what you do. Go to the "Users" part in ebox and create a user. If you want, make the user have the same user/pass as your machine, that way it'll have instant access so long as you are in PDC mode and not FileServer. Go into "Filesharing > Shares" and create a share if you haven't already. Setup this user your just made as the person with access.

I hope that works for you!

503
Just asking, but is that info in the documentation? If so, is there other stuff like that? I just don't wanna bother people with n00b forum posts, but I think I've read all the documentation.

504
Try to setup a Gateway manually. Go to Network > Gateways. And then add it manually there. That should fix it.

What you're saying is, you connect to the VPN and by doing that, you actually lose connection to the network you're one which makes the VPN not work because now there's no way of getting your info to it right?

505
Installation and Upgrades / Re: First time questions
« on: March 31, 2009, 05:09:59 am »
I think you'd make a user Guest and then there's some password anonymous or that's the username. I forget.

What I've done is setup the users as the same ones on the Windows machines and had the passwords the same as on their machines. The not only protects their share from others' eyes, but also gives some credibility to a virus not attacking everyone else provided there was one that went around network hopping. I mean, I took out that prospect by having two subnets on my network so Guests won't be poppin' in crap into my shares. I guess the fact that it works at all it good enough to me.

506
If you're using last 0.11.99 release, it's easier to do.

You need to do the following:

Modify the /usr/share/ebox/stubs/dhcp/dhcp.conf.mas to include these lines:

Code: [Select]
ddns-update-style interim;
ignore client-updates;

You need to add an include file regarding to your chosen interface eth0 in /var/lib/ebox/conf/dhcp/eth0/plugins/pxe.conf which comprises these lines:

Code: [Select]
    option root-path "/tftpboot/";
    filename "pxelinux.0";

The remainder elements must be setup in the eBox Web UI.


eBox see that you have a file in /blahstuffhere/eth0/plugins. Doesn't it? So wouldn't you just have to add that link and point to the plugins folder?

507
Installation and Upgrades / Re: Thin Client
« on: March 30, 2009, 04:30:47 am »
I found out something else. You need some kind of boot information. This is probably what you're getting at. To be able to boot from PXE, you can't just have an ISO, there needs to be some sort of boot loader. I wish eBox came with one or let you choose one, but if you can get a hold of one of those, then you're set.

And if you do tell me because I'm clueless.

508
It also does it if you put something in the "plugins" folder and there's no boot loader for PXE. Then it also complains there and refuses to start DHCP until you move the item out. In fact, it stops giving out IPs randomly. I have no clue why.

509
Installation and Upgrades / Re: Change to a custom subnet
« on: March 29, 2009, 09:00:18 pm »
Oh sorry! I have this working. I just checked my first post. I did this by myself and called a friend to verify. Because 255.255.248.0 isn't valid in eBox no matter what I do unless I DHCP, I changed it to 255.255.0.0. Gosh, I was wondering what you were going on about :P.

My LAN is configured using 255.255.0.0 and 255.255.255.0 for guests. That all works thanks to eBox working properly.

510
Installation and Upgrades / Re: Change to a custom subnet
« on: March 29, 2009, 06:02:15 pm »
5 IPs from the ISP. It is a Gateway. Has 4 NICs.

I'd rather not have to go through loopholes. I wanna keep this IP. I don't mind messing w/ the other ones, but this IP stays. Since there are 4 NICs, one I can dedicate to this kinda thing.

Pages: 1 ... 32 33 [34] 35 36