bozallen

Interested! Pm'd.

Vacancies | Dumpton School

We're experiencing the same issue. Chrome 47.0.2526.73 and Smoothwall proxy using NTLM authentication. I also reported a bug. Hopefully if enough people do this a fix will be released soon.

Easiest thing to do is probably sign up to SEGFL birdbox project and let them worry about the hosting of it. It's free for schools! Then use a cheap USB analogue video capture device in an old PC, comand line FME if the PC isn't v powerful. Done. I really don't think that 9v battery will last much longer than a couple of days! Maybe look at a solar charger for the battery here if it HAD to be wireless. A raspberry pi encoder would be cool, low power consumption and less money than the Axis. I've got a feeling if you did it with FFMPEG it's not compatible with VP6 encoding, which is what SEGFL uses if you were thinking of going that route.

I don't know exact distances, but we think C - A is around 90m. Can you get a 10gbit mini-GBIC? Worth it? There's around 60 clients connecting via A,B,E. B clients will be particularly media heavy. What do people think to using pre terminated fiber from this place Cheap Pre-Terminated Fibre, Pre-Terminated Fiber UK and doing an in-house job? Is it pretty much run-plug-play?

Budget set aside is £5k. Which must cover everything. Cable, switches, installation. Is that realistic? I'd like to steer clear of media converters if I can. Yes, I'd looked at the 2 mini gbic ports on the procurves. Are the 2 ports for 2 separate fiber runs? I.e RX TX twice? Or one port for RX and one for TX?

We're thinking of improving some of the backbone links for our network. Currently all building to building links are via standard cat 5. Not exactly "by the book", but it's worked well for over 5 years running at 1 GigE. We're thinking of replacing these with fiber, however I've never worked with fiber and I'm not sure of the most efficient network layout or most cost effective method of installation. The attached pdf shows all of our current switches and links. As you can see from the diagram switch C is our 'central switch', a procurve 1800-24. Would replacing links C-E , C-B and C-A with fiber be best? Or just running a single 10gbps fiber link and creating a second 'core switch' for the building on the right? (Ignore C-F, it's non-critical) As for installation, a pull through exists between the core switch and the building on the right. Is a in house install viable or can anyone recommend good companies in the Dorset area for quotes? Also, would we need different switches? The procurves have modules to support fiber, but possibly not enough for our core switch to support multiple fibers. Any advice on how others would tackle this would be great! Network Map.pdf

Sadly Fatmas I never solved this one. Ran out of time in the end. We just use Clonezilla on a USB drive pulling images from a fileserver at the minute. I'm sure, by far, not as efficient as Fog but it still saves hours / days on manual installs! If you find a solution be sure to let us know!

I've also tried querying the ports of both the DHCP and FOG server. Neither DHCP Server or FOG is listening on 4011 UDP FOG is listening on 69, DHCP Server is not DHCP Server is listening on 67 & 68, FOG is not. Any one any clues why it's not working??

@arcath On the client I select PXE boot from the boot selection menu, enters PXE boot screen, Client MAC.... (MAC Address) GUID... (GUID) DHCP.... (about 1min 30sec here) Client IP... 192.168.43.91 Mask 255.255.255.0 DHCP IP 192.168.43.253 (Correct from our scope) PXE-E55 ProxyDHCP: No reply to request on port 4011 PXE-MOF: Exiting Bootmanage PXE ROM @kevbaz I've never installed or have any experience of WDS. I can't see a service / server role / Administrative Tool for it. Could it be hiding elsewhere or can I assume that's not the problem?

Nothing is set in server options only scope options. I'll give 66 / 67 a go in there... No. Same error when 66 and 67 are set in both server options and scope options.

My server has 3,6,15,44,46 and I've tried it with and without 66 / 67. Same error.

Windows firewall is disabled. No hardware firewalls internally. Port 4011 is for proxyDHCP right? Does this need to be setup on the DHCP server also? Wikipedia states... The Proxy DHCP service may also be run on the same host as the standard DHCP service. Since both services cannot share port 67/UDP, the Proxy DHCP runs on port 4011/UDP and expects the extended DHCPDISCOVER packets from PXE Clients to be DHCPREQUESTs. The standard DHCP service has to send a special combination of PXE options in its DHCPOFFER, so the PXE client knows to look for a Proxy DHCP on the same host, port 4011/UDP

Hi, I've just installed FOG on Ubuntu to try it out. It sounds cool! I didnt enable FOGs DHCP service as we're already running Win 2003 DHCP. I followed the FOG documentation for Win DHCP and did the following... Highlight the Scope Options for the subnet Scroll down the list of options to 066 "Boot Server Host Name". Check the box next to option 066. Enter your tftp server's ip address check option 067 "Bootfile Name" and enter the name of the bootimage "pxelinux.0" However when I boot any client via network boot the client spends ages on the DHCP section, gets an IP address then I get the message PXE-E55: ProxyDHCP: No reply to request on port 4011. I tried removing the 066 and 067 entries and booting a client via LAN, the same error message. We only have 1 subnet, on VLAN1, a couple of HP Procurve 1800gs (on the servers and core switch) and the rest HP Procurve 1400s. Around 100 clients. I've tried a client on the same switch as the servers. Nothing. Any ideas? I tried googling but most responses are WDS / Ghost / etc specific.