BatchFile

they do when they're not in a laptop...

I've no idea which forum this should be in so feel free to move it! Simple question: Does anyone know of a courier that will accept laptop batteries anymore? We had a slip of the mouse and ordered the wrong ones from an eBay seller; the seller will swap them, but we can't find a courier that will take them as they are categorised as hazardous goods... We've tried all the usual suspects: Post Office DHL TNT UPS etc.

I'll sketch up a diagram in a bit - but re not sending out the IPs, did you remember to set the PVID to 2 and Untag (U) the port the green's connected to?

I think it's the open source SmoothWall version @tj2419 is talking about - that's certainly what I'm talking about - it's a simple (to set up) firewall, DHCP etc. Mine's currently running on a 9 year old PC that used to be in one of the IT rooms!

I think others have answered this while I was having a few days off :-) What I did in the BYOD VLAN was tagged (T) all the ports that would carry the traffic on any switches EXCEPT the port that the SmoothWall (IpFire in my case) GREEN connects to, which is untagged (U). Set the PVID of the green port to 2 as well. In the "Other" (School devices) VLAN, all I had to do was remove ( ) (that's no T or U) the green port. Turn on DHCP server on the Smoothwall, set its red to pick up an IP address from the main school DHCP server, configure it as a transparent proxy to point all traffic at either your main school proxy or LEA servers, and that's about it. For troubleshooting, I found it useful to configure another port on the switch in the same way as the "green" (ie U in BYOD VLAN, PVID=2 and nothing in school VLAN), to connect a laptop in so you've got a wired device on the BYOD VLAN to verify DHCP etc taking ruckus out of the equation.

It's all going well now - I've got a teeny tiny Vlan2 running around a core switch wth an AP, Zonedirector and proxy with DHCP as above (went with IpFire in the end - I just like it) and it seems to work well. Devices connecting to the AP on the BYOD lan are now getting BYOD addresses (192.168.x.x) rather than "school" ones (10.x.x.x) and devices connecting to the other LANs are getting the right ones too. All that's left to do now is a bit of repatching, joining a switch in each of the other cabs to the core switch I've been fiddling with, and tagging appropriately, which I'll do in half term. Just one last question (hopefully): I should be able to avoid it, but just out of curiosity what happens if there's an unmanaged switch along the route? do they untag packages or just pass them on blindly?

This is the latest high quality and well thought out package bought in by a department. it's (paper) worksheets, supported by a website which, after the students have logged in, serves up interactive activities in the form of Excel sheets (and that's about all it does). The excel sheets are packed to the rafters with VB and run fullscreen. Once completed there's a certificate to print and stick in a "passport". It seems fine as long as you: are running at least Office 2010 :rolleyes:Turn off protected mode :confused:Disable data execution prevention :(Enable all macros to run :eek:Allow Access to the VBA project object module (and have the wind blowing in the right direction) I can't help thinking there's a better way of serving these activities up? even flash would be an improvement on this! ...now where did I put that Office 2010 GPO...

Thanks both and Edugeek - still the best substitute for knowledge and training! Will have another go and no doubt be back.

been doing a bit more poking around (carefully!). What's the difference between tagging (or untagging) a port in a VLAN and setting the PVID on it?

I'm trying to get my head around VLANs in order to get a suitable BYOD system going. I've given up with wpad and pac as I think it'll end up with a queue at our door each lesson. I want to have a proper go at this next week (half term), but had a preliminary look yesterday and last night and am even more confused now than I was before - it's entirely possible that I've fundamentally misunderstood something here! Our Ruckus system sends out two WLANs for our stuff here (one for our laptops etc whose key rarely changes, and one for stuff such as staff phones whose key does change periodically). There are currently no (well, one, I suppose) VLANs; I haven't configured any - everything is set to VLAN1 and PVID1 as it came out of the box. I'm adding another WLAN, with AD Authentication, for pupil BYOD. Ruckus appears to be able to add a VLAN tag to traffic from a particular WLAN, so I'm setting the BYOD to VLAN2. So far I think I'm ok - now comes the sketchy bit that I need to check; please can someone confirm that the logic here is correct before I break my network (we have Netgear FSM726 switches if that helps / makes a difference)? I have a Smoothwall transparent proxy to sit between the VLANs, provide DHCP for the BYOD, and send everything to the LEA proxy; so I need the "green" connected to VLAN2 (that is a port with a PVID set to 2) and the "Red" connected to VLAN1 (like everything else on the network is at the moment)? The port that the access point comes into the switch on needs to be a trunk, as it carries traffic on both VLANs, as do all the connections between switches that carry BYOD traffic? Does the zonedirector need a trunk as well or does the traffic go straight from the AP into the network? Here's a diagram of what I'm trying to do in case it's easier (just one switch shown here) Now, to muddy the waters somewhat, I tried setting that up last night, setting green to 10.x.x.6 and red to 10.x.x.7 . before fiddling with any switch port settings. With my workstation connected to the same switch (wired) I set off a ping, pinging both addresses and another which is an-other server. When I changed the PVID of the green port on the switch, I was expecting to stop getting pings back from it, but I expected the red to carry on replying; but they both stopped... "an-other" kept going - reversibly and reproducably - what's going on there please? Many thanks!

Nah, needs to be "Windows....Why?"

I'm working to implement BYOD with Ruckus by following this: http://theruckusroom.typepad.com/files/byod-with-ruckus-0712-3.pdf I'm also wanting to use Ruckus's auto-proxy function to tell BYOD clients what to do with their internet traffic, probably sending all of it to a smoothwall (or ipfire) proxy so we can log it before forwarding it to the LEA servers. It'd probably be useful, though I realise not without risk, to allow them access to the internal network too to get on the intranet etc. I've no experience whatsoever with wpad; but I've adapted the one below from an example I found. Is there anything else that has to be in there for it to work as described above? function FindProxyForURL(url, host) { // If the requested website is hosted within the internal network, send direct. if (isPlainHostName(host) || shExpMatch(host, "*.local") || isInNet(dnsResolve(host), "10.105.16.0", "255.255.255.252") || return "DIRECT"; return "PROXY 212.219.207.41:8080; PROXY 212.219.207.40:8080"; PROXY 212.219.207.43:8080"; } 10.105.16.0 is the start of our IPs, 255.255.252.0 is the subnet 212.219.207.4x are the LEA proxys - which I can replace with an internal proxy before I switch it on.

I've actually revived the old fan with a combo of wd40 and 3in1 oil (bearings had seized), and it's now Back in and working fine. I'd still be interested in the answer though, if anyone knows.

Hoping someone here can give me a hand with an electrical engineering question: I've replaced the cooling fan in our bosch oven with an aftermarket one (oem ones are £150, this one fits and works and was £17). The new one is significantly more powerful and therefore noisier, than the original and I'd like to stick something in series with it to slow it down. I've calculated it as though it's dc and assumed that everything.behaves like a resistor, as that's the only way I know, and I am hoping that some kind soul can tell me if what I've worked out is valid. Right: Fan is 23w and 230v ac. I'm assuming that a voltage drop across it of about a third will do the job, so I'm proposing putting a lightbulb in series with it as a resistor. For the fan, using p=vi then v=ir, I calculate that it has a resistance of 2300ohms. Given that I want a third of the voltage to be taken by a resistor (the bulb) I need a bulb with a resistance of about 1000ohms. I've calculated that a bulb rated at 230v and 60w will have a resistance of 881ohms, which should do the job nicely. In this application it'd only be getting about 70v, so should last forever, the fan would take the other 160v and work nice and quietly.

A simple question... How do you use "net use /delete" to delete a conection that is listed by "net use" but doesn't have a drive letter or lpt assigned?

like setting up VLANs for BYOD and stuff you mean? if so that's what I'll need.

after failing to find what's causing an intermittent problem on the network, having checked server logs, wiresharked them and restarted everything, I think it's time to look at some new switches (as the Netgears we've got are 10 years old). I've just started to look at my first chouice supplier for this kind of thing, and I've hit a question: What's the difference between a Layer 2 switch and a Layer 3 switch? I thought that was more to do with how you plugged the network together - but it seems the hardware's different judging by this: Managed Switches | Network Switches | Active Networking | Shop By Type | Videk | Network Systems and IT Solutions Can someone enlighten me please?!

Yup, can confirm that this was fixed by nbtstat /R

This reminds me of the Jeb's Jobs video: "This is technical support!......... Well what do you suppose we do?!" I'll find a link in a minute... Here we go:

I'm just wondering if this might be a netbios thing and just need a nbtstat /r... (but I can't get hold of either laptop to check at the moment)

Either one or both - same problem. It also occurs when on my workbench which is a different set of switches and APs

In that order... No, 7. No, DHCP. Not according to the ipconfig /all.

Unfortunately this laptop has gone, along with its owner, on the annual ski trip, so it'll be next week before I can do anything further on this one. Just when it was getting interesting, too :-(

Quicker than I thought it'd be but no difference, even after another /flushdns

What, Now?! Oh well, I suppose they'll fail over to each other won't they...