IrritableTech

Turned off my last 2003 server today after successfully migrating services to a 2012r2 replacement.

This issue was fixed by Google, and they rang everyone who's reported it back to confirm. Just checked mine is syncing - no issue here. I use 4.0.3. How are you authenticating, OAuth or username and password (I think they were phasing out the latter).

Looking at your Ruckus controller... Configure - Access Points - Access point groups. In the port settings area, is your lan port setup as trunk, general or access?

Good news @JJonas Yeah the port which your AP is plugged into (J24) should probably be Untagged VLAN 1 and Tagged VLAN 2. On the Ruckus SSID settings page the ACCESS VLAN should be set to 2.

We've just invested in Smartdesk. Pretty much everything is working as it should. One thing I'd like to do is bundle tickets into one problem. The feature list states "Problem creation (linking of multiple tickets into one identified problem)" Can't for the life of me work out how to do it though! Sure I'm being silly. We're on 2.6.2197 MR3[h=4][/h]

Excellent. I'm suspecting your servers gateway address is the issue now.

Ok - that sounds to me like the smoothwall either doesn't have the right IP setup on its (v)NIC, or it's not tagged in the right VLAN - probably the latter 'cos I just realised my suggested config didn't account for the SW! [edit] Where does the smoothwall plug in? Did you say previously you've utilized another NIC for the Guest stuff? On your DHCP server. What are it's NIC settings? IP is 10.103.20.11, but what is the subnet and the gateway?

No problem, lets keep trying... You and @JJonas both from the same establishment right? :-) Plug a laptop into J24 and give it a fixed IP. Lets say 172.16.1.100 SN 255.255.255.0 GW 172.16.1.3 Use this vlan config on your switch... Ping 172.16.1.3 (switch) does it work? Ping 172.16.1.1 (smoothwall) does it work? Ping 10.103.20.11 (server) does this work? If all those work, then try setting your laptop to DHCP - does it get an address? Try those pings again just to be sure DHCP is sending out the right subnet and gateway. If everything is working up to now, replace your laptop connection (J24) with the AP, and change your config to the below. Ensure your ruckus is set to tag your guest wifi with VLAN 2. Does the AP show up as connected? Go through the same tests. Connect to the wifi network with a fixed IP. Ping the same devices. Then try to get a DHCP lease. Ping the same devices. If this doesn't work... where exactly did things break?

Reboot - I was clutching at straws a little, sorry. It's magic. But really, the client broadcasts asking for a IP address. The switch acts as a proxy and knows the IP address of your DHCP server (the ip helper command). So it forwards the request (in simplistic terms): Request from MAC ADDRESS in this SUBNET. The DHCP obliges allocating an address from the correct subnet and sends the DHCP lease back and the switch deals with sending the info back to the client. A much better explanation that I googled... https://allaboutmylife.wordpress.com/2007/10/17/ip-helper-addresses-for-dhcp/

Hang on what thinks it isn't plugged into the switch? You were trying the laptop right? Untagged = data which is not tagged with a vlan, tag it with this one. It's an odd term. Tagged = data tagged with this vlan may travel over this port. Where the laptop connects needs to be untagged. Where the AP connects needs to be untagged vlan 1, tagged vlan 2.

I think you'll find J24 will need to be untagged in vlan 2 to test on the laptop. It was ok tagged on the AP, becuase the AP is tagging the traffic - your laptop wont be (unless you tell it too). The other thing which I remember from setting up our 5412 was that I had toruble getting routing working. Luckily I was doing this on a test network, and a simple reboot got routing working - It shouldn't have needed a reboot, but it did.

I wonder how many of them will use their official parliamentary email address to register with apple? The simple iMessage trick that lets you text almost any MP without knowing their mobile number

Parody accounts are allowed on twitter, but if the actions become defamatory it can cross into a legal issue. Education is always key - you can play cat and mouse all you like but that might be the most fun part for the students. A timely eSafety assembly (which Oftsed like in reaction to eSafety issues, but don't like as the only eSafety training) highlighting how issues like this have got people in very deep trouble with the authorities might be enough to nip it in the bud. If your community support officers or school police liaison officer is able to run this, that might help too.

@Davit2005 is correct. You DHCP scope needs to issue the gateway 172.16.1.3 (the IP assigned to your switch) as it will deal with where to route the traffic after this (either your default vlan, or your edge router). Unless.... How are you planning to filter your guest clients? Are you going setting a proxy on them or will the smoothwall become the router for the guest network? If so, once you've checked the network works, you'll need to change the gateway address in your DHCP scope to filter devices.

From the 1st of July all freefone numbers will be free from all mobiles - New Ofcom rule - Ofcom | Campaign to explain major changes for telephone users My wife will be glad to hop onto the O2 network at work if that comes about. She loves three, except in her office!

The command is "ip routing"

We've run on windows successfully for some years now. Windows fit's in better here for similar reasons, and linux didn't prove to be too much of an advantage.

Looks ok at a glance assuming your ports are correct. Have you created a dhcp scope for 172.16.1.x on your server? Are addresses being leased out?

Someone with more hands on knowledge of Smoothwall today might give you a more complete answer, but I think you can use your smoothwall as both DHCP and DNS server for your BYOD network if you like? Otherwise you'll need ip-helper (or the equivalent) setting on the BYOD VLAN and a route to the DHCP server (not forgetting any ACLs which may be set) and DNS if that's your preferred plan.

Hope to get rid of the last at Easter.

Seems I was wrong then... Good to hear. :-)

I have no experience with these, but I hear they fail all the time. Perhaps recent stock is improved though?

Just had the following... We have identified a cause of the authorization failures GADS has been experiencing. We are currently in the process of releasing a change, and we expect to resolve the authorization issues within the next hour. We will provide more information into the root cause once we have completed our full investigation.

Working here too. Jobs to be done now. :-)

Our XML file isn't compatible with v3 - tried removing GADS entirely (because it seems the update process from 4.0.1 to 4.0.3 doesn't entirely get rid of the former) and installing v3.something then upgrading through the update tool. Still getting the same error. :-(