Posts made by szecca1

@Tom-Elliott I completely understand and fully appreciate all your help. I just updated the trunk and got the wolbroadcast plugin installed. Is there anything else I need to do or technically now it should work?
@Joseph-Hales The Fog server is probably more authenticated than my computer is as it no longer needs to authenticate to out iPrism and my computer still does every so often.

@ch3i Yes I am running goverlan from my machine which is on the 10.1 VLAN and FOG is a VM that also running on the 10.1 VLAN

@ch3i Yes, thats what is confusing. I tested today turning off a computer in a different vlan and then the computer woke right up with my wake on lan from Goverlan but wont do the same in FOG

@Tom-Elliott The wol broadcast plugin is not in the plugins for some reason so I cant install that

I apologize for the long delay, I have been very sick. I am running FOG version 1.2.0 and am able to Wake on LAn with a program call Goverlan.

I saw this on the wiki site
https://wiki.fogproject.org/wiki/index.php/How_to_use_the_wakeonlan_perl_script_instead_of_etherwake.exe
wasnt sure if that was relevant.
We are running Avaya and Nortel switches through our district and have opened the ports, at least we believe unless we are missing something. The wake on lan works on the same vlan but crossing vlans is wake it stops.

Good afternoon,

I have trying to test wake on lan through fog over different vlans. On the same vlan as the fog server, wake on lan works perfectly, but when I try wake on lan over a different vlan thats when the packet seems to not go through. For example:

My fog server IP is 10.1.0.119, if I try to wake on lan a pc with an IP address of 10.1.x.x, wake on lan works perfectly. I then tested computers with an IP of 10.2.x.x and an IP of 10.3.x.x, and the computer never wakes up. I used the same computer in all locations so the settings are the same just something is blocking the packet from going through.

Anyone have any ideas?

Hey guys sorry its been so long, I just wanted to test a few things before I came back here. Everything is working perfectly. Thank you so much!!!

@szecca1 I just tried that command and it says failed to create symbolic link as directory /Volume1/Volume1 does not exist

@Tom-Elliott Should I do this before I try to upload an image?

@Wayne-Workman The image is stuck in /images/dev.

I am guessing that would be the problem

@Wayne-Workman I just started a new upload to test again but it is working. It’s when I go to download the image on to a client that says “to setup download task, you must first upload an image.”

My first impression is that the fog server doesn’t know where to pull the image file from but I dont know if I am right. I am uploading another image just to be sure right now.

@Wayne-Workman I’m only going to have 1 FOG server on my network so would the location plugin be needed?

Why is the image that I uploaded not being detected by FOG? I probably set something up wrong, didn’t I?

@Wayne-Workman Should I only have one storage node?

What is the location plugin?

@Wayne-Workman I do have two storage nodes, one that is the default and one I added called test. The default one had the admin login, so I changed that. Now it seems that is where it is pulling the login as now it is saying this error

“To setup download task, you must first upload an image”

Which may seem pretty basic but I already uploaded an image?
And unless I am using this location plugin by accident, no I don’t think I am using it

@Wayne-Workman nevermind, I just tried to change the password of the NAS login to see if thats where the login info was being pulled and it still gave the same admin/NEBULA password. I am now completely unsure where this password is being pulled from.

@Wayne-Workman Yea I’m starting to love this NAS as well.

The credentials it is giving is no where on the fog server. I had entered credentials in TFTP server-> FOG_TFTP_FTP username/password and also storage management username/password. The only thing I can think of is when I go to log in to my NAS server, the admin/NEBULA password is used, but 10.1.0.119 is the IP address of the FOG server.

Am I going to have to change the login to my NAS server to fog/password?

@ch3i You guys are awesome, it was the firewall and now the image finished uploading perfectly. But in testing, I wanted to send the image to a client and when i did i get an error.

“Download task failed to create for client with image.
FOGFTP: Login failed. Host: 10.1.0.119, Username:admin, Password: NEBULA, Error:ftp_login(): Login incorrect.”

I havent changed anything since the upload worked so where would this be pulling that username and password?

@ch3i Just so I understand, the password I have in Storage management -> management password should be the same password that is on the NAS box?

If thats the case I just did that and still getting the same message.

I set the fog user on my NAS box to password and in the storage management -> management username/password I put fog/password to match the NAS.

Is this how that should be setup?

@ch3i what password does it need to have??

@Wayne-Workman Ok did that and even created an administrator account on the Synology box with the same credentials just in case and still getting the same issue.