• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Seb
    3. Posts
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 27
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by Seb

    • RE: Where are you located ? Please Reply..

      Bournemouth, Dorset, UK

      posted in General
      S
      Seb
    • RE: APIPA, domain joining, PXE operation not permitted

      Yes, all sorted šŸ˜‰

      posted in FOG Problems
      S
      Seb
    • RE: APIPA, domain joining, PXE operation not permitted

      OK, I have sorted the 403 error now.
      I edited /ect/apache2/apache2.conf, adding a new line at the bottom with
      [CODE]ServerName localhost[/CODE]
      And restarted the services with no errors

      I’m now going to look at my domain joining and naming issue.

      [B]EDIT[/B]

      Just imaged two PCs, in the fog log on C both get this error

      [CODE]HostnameChanger Domain Error! (ā€˜Unknown Error’ Code: 2)[/CODE]

      [SIZE=3][FONT=arial]There was a typo in [COLOR=#555555]FOG_AD_DEFAULT_OU - this must be the issue[/COLOR][/FONT][/SIZE]
      [COLOR=#555555][FONT=Ubuntu][SIZE=3][FONT=arial]I’m a frickin idiot[/FONT][/SIZE] šŸ˜• [/FONT][/COLOR]

      posted in FOG Problems
      S
      Seb
    • RE: APIPA, domain joining, PXE operation not permitted

      [COLOR=#000000][FONT=arial][SIZE=3]Hey, cheers for the reply.[/SIZE][/FONT][/COLOR]
      [LIST]
      [][COLOR=#000000][FONT=arial][SIZE=3]On version 1.0.1 (i think,) we had the issue with APIPA whenever i put option 67 in DHCP for it to find a real file, such as unidionly.kpxe. I used to change it to something like ā€˜unidionly.kpxeeee’ and it wouldn’t mess with IPs. Not an issue now anyway though. :)[/SIZE][/FONT][/COLOR]
      [
      ][COLOR=#000000][FONT=arial][SIZE=3]I’m almost 100% certain that it was giving names out in the format above, i’ll be able to double check when i get it back up.[/SIZE][/FONT][/COLOR]
      [*][COLOR=#000000][FONT=arial][SIZE=3]So am i right in putting :[/SIZE][/FONT][/COLOR]
      [CODE]FOG_AD_DEFAULT_DOMAINNAME : ā€œDomainā€
      FOG_AD_DEFAULT_OU : OU=Workstations,DC=ā€œDOMAINā€,DC=net
      FOG_AD_DEFAULT_USER : ā€œuserā€
      FOG_AD_DEFAULT_PASSWORD : fogcrypt’d passsword[/CODE]
      [COLOR=#000000][FONT=arial][SIZE=3]

      Because with versions below 1.0.0 in the user field I had domain\user[/SIZE][/FONT][/COLOR]
      [][COLOR=#000000][FONT=arial][SIZE=3] I will try and create one new image and see if that changes anything[/SIZE][/FONT][/COLOR]
      [
      ][COLOR=#000000][COLOR=#000000][FONT=arial][SIZE=3]If i go to the address in a browser i get [/SIZE][/FONT][/COLOR][/COLOR]
      [CODE]ForbiddenYou don’t have permission to access /fog/service/ipxe/boot.php on this server.
      Apache/2.2.22 (Ubuntu) Server at IP Port 80[/CODE]
      [/LIST]
      [COLOR=#000000][FONT=arial][SIZE=3]Have permissions been messed up on the var/www/fog/service/ipxe folders?[/SIZE][/FONT][/COLOR]

      [B]EDIT[/B]
      I have tried to reset permissions using
      [CODE]sudo chown -R www-data:www-data /var/www/fog
      sudo chown -R fog:www-data /var/www/fog/service/ipxe/[/CODE]

      and then [CODE]sudo service apache2 restart[/CODE]

      with still no luck, when i restart apache services i am prompted with this…
      [CODE]Restarting web server apache2
      apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
      … waiting apache2:
      Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName[/CODE]

      posted in FOG Problems
      S
      Seb
    • RE: APIPA, domain joining, PXE operation not permitted

      In regards to domain joining, i did check the individual host AD setting and it all looked fine. It pulled across successfully from fog config

      posted in FOG Problems
      S
      Seb
    • APIPA, domain joining, PXE operation not permitted

      Hey guys,

      First off i have to apologise for the range of issues and huge wall of text approaching.
      Really sorry :oops:

      I was on ver 1.0.1 and when PCs booted up, they could not log in because they had been put onto the 169 range, however imaging worked and named themselves correctly.
      I have upgraded to 1.2.0 and the APIPA issue was resolved, however now when i image a PC they no longer join the domain and rename themselves to something random such as - ā€œTBO193753-1123ā€ or similar (TBO being the first few letters of our domain.)

      I have looked into the ad settings within fog config and made sure that username only has the username within and is not in the format of domain\user. The AD account has not changed, same password, permissions and it’s not expired.

      I think that when i built these images last year they [U]may[/U] have been joined to the domain when i uploaded the image, is this where i am going wrong. Has the procedure changed? The images have worked fine when on versions below 1.2.0
      Do i have to rebuild all my images? šŸ˜ž

      My second issue is that when i was looking at this last night, my server suddenly died with a memory error.
      I have since fixed the issue, however after i got the server back online the clients get the following error during iPXE boot.

      [url]http://ip.address/fog/service/ipxe/boot.php[/url]… operation not permitted ([url]http://ipxe.org/410c613c[/url])
      Could not boot: Operation not permitted ([url]http://ipxe.org/410c613c[/url])
      PXE-M0F : Exiting PXE ROM

      I have followed this thread here with no luck - [url]http://fogproject.org/forum/threads/stuck-at-boot-php-operation-not-permitted.10706/[/url]

      Thank you guys in advance, love ya

      Seb

      posted in FOG Problems
      S
      Seb
    • RE: 040ee119 error on boot

      [quote=ā€œTom Elliott, post: 28604, member: 7271ā€]Thanks for the support. With which undionly are you getting the issues with the 380’s? And which error?[/quote]

      Both undionly.kpxe and undionly.kkpxe on [url]https://mastacontrola.com/ipxe/f473-GOOD/[/url] provide very similar results (100% working on dell 3010)
      It is the same 040ee119 error on the 380s, it then reboots and trys again.
      I have also since found that dell 755 and 760 have the same issue.

      So it seems like just our older models.

      posted in Bug Reports
      S
      Seb
    • RE: 040ee119 error on boot

      Both undionly.kkpxe and undionly.kpxe work 100% of the time for my Dell 3010s with realtek controllers.
      However now our 380s with broadcom controllers fail almost evertime with the previous and get stuck in a boot loop.

      Awesome work, i really appreciate everything you guys are doing. šŸ™‚

      posted in Bug Reports
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œJunkhacker, post: 28386, member: 21583ā€]try the latest undionly.kpxe, a longer max wait time for DHCP responses has been added and it seems to help a lot[/quote]

      Where can i find the latest undionly.kpxe? I’m sort of losing track of all the ones that i have tried.

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      Is anyone else getting this issue still? Or have others been sorted out? Maybe there is something wrong with our spec?
      We are currently running ubuntu 12.04, should i try going to 13.04/13.10?

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œWolfbane8653, post: 28273, member: 3362ā€]
      Just butting in here with some info on the model’s network card:

      [B]Dell Optiplex 3010: [/B]:eek: two possibilities depending if Standard release or AIO release )
      [I]Realtek 5M02W Integrated Controller[/I]
      [I]Broadcom 57XX Integrated Controller[/I][/quote]

      Cheers, the ones i’ve looked at are all ā€œ[I]Realtek 5M02W Integrated Controllerā€[/I]

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 28248, member: 7271ā€]Try all of these if you can, and report back:
      [code]wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe
      wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kkpxe
      wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.kpxe
      wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.kkpxe
      wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.pxe[/code][/quote]

      All these tests are done in a room of 30 Dell 3010s as they are the most common machines we have.
      [LIST=1]
      []50% work first time, the rest take 2-10+ retries
      [
      ]80% work first time, the rest take 2-10+ retries
      []0% work, restarts continuously
      [
      ]0% work, restarts continuously
      [*]0% work, restarts continuously
      [/LIST]
      Is there any additional information you require?

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 27829, member: 7271ā€]try:
      [code]sudo wget -O /tftpboot/undionly.kpxe https://mastacontrola.com/ipxe.kpxe[/code]

      This should have the drivers for all the cards that IPXE has and should allow initialization of the device.[/quote]

      With this one in a room of 30 dell 3010s every one continually restarts and loops when they get the 040ee119 error.

      I tried [URL=ā€˜https://mastacontrola.com/undionly.kpxe’][I][SIZE=12px]https://mastacontrola.com/undionly.kpxe[/SIZE][/I][/URL] and with this one in the same room and around 50% of them got to the menu first time, the others would restart between 2-5 times before working.

      I tried this again and it was different pcs every time that worked.

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 27768, member: 7271ā€]When you say ā€œrollā€ back to 0.33 build, do you mean the revision where it was still known as 0.33? I would say that’s likely not going to work in your situation.

      Reason being is 1312 IS the undionly.kpxe that was being use.[/quote]

      Sorry, that was a typo, i meant 0.32b

      thanks for all you’re doing guys, we are running a ubuntu 12.04 LTS server, we tried to upgrade to 14.04 but it said our dell 2950 wouldn’t cope.

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      I have quite a few, all produce the same intermittent issue with the menu.

      We have the following models

      Optiplex 3010
      Optiplex 7010
      Optiplex 390
      Optiplex 380
      Optiplex 760
      Latitude E6420 & E6500

      All the other features of fog work well, we are still capturing and deploying images across the network and just enabling and disabling the boot option in dhcp as and when we need it. (Havent tried any win8 or multipoint 2012 image captures yet, always failed on .33)

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      I have tried every config file on the other thread now with to no avail with our various dell PCs, the one that has been recommended (1312) works intermittently.

      I really do love fog, and it has been a MASSIVE tool here at our organisation. But we may have to roll back to 0.33 build.

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 27574, member: 7271ā€]Sorry I made a typo, and have corrected it above. The link to get it from should be:
      [url]http://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe.INTEL[/url][/quote]

      ah, i have tried this file now.

      It’s still coming back up with the 040ee119 error and then boots after 5 or so attempts.

      I previously had luck with [URL=ā€˜https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw’][I][SIZE=12px][FONT=Consolas]https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/FONT][/SIZE][/I][/URL][I][SIZE=12px][FONT=Consolas] [/FONT][/SIZE][/I]

      [I][SIZE=12px][FONT=Consolas]But it suddenly stopped working after an hour[/FONT][/SIZE][/I]

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 27569, member: 7271ā€]It’s already back up.[/quote]
      still getting a 404

      [url=ā€œ/_imported_xf_attachments/0/797_IMG_20140520_131808.jpg?:ā€]IMG_20140520_131808.jpg[/url]

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œSeb, post: 27563, member: 7969ā€]Hi, i re-tried [FONT=Consolas][url]https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/url] [/FONT]

      [FONT=Consolas]manually instaed of using the command and this has worked for me.[/FONT]

      [FONT=Consolas]Thanks guys [/FONT][/quote]

      Hi,

      Suddenly stopped working.

      Made no changes but it now errors out 4 times again.

      I will maybe wait for your website to be back up to get the intel version.

      posted in FOG Problems
      S
      Seb
    • RE: IPXE issue

      [quote=ā€œTom Elliott, post: 27557, member: 7271ā€]Sorry, I’m currently upgrading my Virtual Host system at the moment, so the website just went down. It’ll be back up in about 20 minutes or so I’m hoping.[/quote]

      Hi, i re-tried [FONT=Consolas][url]https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/url] [/FONT]

      [FONT=Consolas]manually instaed of using the command and this has worked for me.[/FONT]

      [FONT=Consolas]Thanks guys [/FONT]

      posted in FOG Problems
      S
      Seb
    • 1 / 1