Windows Firewall is disabled. There are Windows 7 computers on the same subnet as the server which have working FOG services so the antivirus is not blocking the FOG service.

Unfortunately, the command recommended by Jose did not help, though I appreciate the ideas.

I’ve come across a few other threads where people have similar problems, but I haven’t seen any direct solutions related to this specific Windows 7 subnet issue. I’ll keep working on it though.

In my experience, that is correct.

Computers running XP have no problems with the FOG Service connecting on any subnet which suggests the server could communicate with all computers on all subnets previous to adding Windows 7 systems to our network. Furthermore, host registration and imaging works for ALL computers regardless of operating system which suggests the server can STILL communicate with all computers on all subnets.

For some reason, though, the FOG Service specifically installed in Windows 7 does not communicate with the FOG server when on subnets different from the server. And just to note, there are computers running XP with FOG Services working correctly on the same subnets as computers running Win7 with FOG Services not working.

We have a similar problem to this.

We have FOG 1.1.0 and Ubuntu 12.4 working over multiple subnets. We have a couple models of computers running Windows XP and a few models running Windows 7 (recent OS addition to our network).

PXE booting and imaging works great for all machines. After imaging any machines running XP, the FOG service normally reboots the machines to change the computer name to match the registered host name which works across all subnets. After imaging the Win7 machines, we expected the same routine, but for an unknown reason, only the FOG service on the computers on the same subnet as the FOG server can communicate with the FOG server. All other Win7 machines on different subnets give constant error messages in the log file of:
[CODE]7/31/2014 6:15 PM FOG::GreenFog Sleeping for 1 minute.
7/31/2014 6:16 PM FOG::TaskReboot Attempting to connect to fog server…
7/31/2014 6:16 PM FOG::DisplayManager Attempting to connect to fog server…
7/31/2014 6:16 PM FOG::UserCleanup Failed to connect to fog server!
7/31/2014 6:16 PM FOG::UserCleanup The server committed a protocol violation. Section=ResponseStatusLine
7/31/2014 6:16 PM FOG::UserCleanup at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at FOG.UserCleanup.doWork()
7/31/2014 6:16 PM FOG::AutoLogOut Sleeping for 1 minute.
7/31/2014 6:16 PM FOG::HostnameChanger Attempting to connect to fog server…
7/31/2014 6:16 PM FOG::PrinterManager Attempting to connect to fog server…
7/31/2014 6:16 PM FOG::DisplayManager Failed to connect to fog server!
7/31/2014 6:16 PM FOG::DisplayManager The server committed a protocol violation. Section=ResponseStatusLine
7/31/2014 6:16 PM FOG::DisplayManager at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at FOG.DisplayManager.doWork()[/CODE]

[QUOTE]Today I deployed a room of 24 PC’s and PXE booted all of them. FOG started deploying the first ten on its list. The remaining fourteen displayed a message like “Waiting for a slot: there are 0 to 13 PC’s in front of me” depending on where it was in the queue.

After these fourteen had been in the queue for about nine minutes, the position in the queue for all the remaining PC’s slowly changed so that by ten minutes in the queue they all reported “0 PC’s in front of me”.[/QUOTE]

[QUOTE]As the deploying ones finished and cleared from the task list the next one in line started deployment until all 24 were deployed. It’s almost as if the deployment engine either at the host or server end lost communication after 10 minutes then without any fresh information to go on, used zero as a “best guess”.[/QUOTE]

This has been happening on our system as well exactly as fre2709 has described.

FOG 1.1.0
Ubuntu 12.4

Our server is on 1.1.0. We upgraded from 0.32 a couple months ago. The day the problem appeared, we had deleted an image that was associated with 50+ computers, though we’ve done no checking to see if they’re related.

This started in my department’s FOG server as well on Thursday, July 24. There are up to 1800 blank, no name images in the image list, but they can only be seen from the drop down menu when associating an image with a group. If “List All Images” is clicked, a blank page appears.

We’re still trying to figure out why the server started creating the image entries, but we believe the count got to 1800 when someone tried to list images during full host registration, and kept hitting enter to see the ‘rest of the list’. Instead of going to the end of the list, hitting enter kept making more blanks.

Has anyone else come across this odd problem?