MrJDH

This worked, or at least kick-started the setup. All working. Thanks.

Thank you for that. I guess my main concern was setting it all up for the URL to fail, and whether anyone could confirm for sure whether the Gmail and Cloud Platform strings were the only ones that would be accepted.

Hello. Just in the process of reading through https://docs.microsoft.com/en-gb/azure/active-directory/saas-apps/google-apps-tutorial to configure SSO. At step 4 and 5, the sign-on URL for the SAML configuration specifies only Gmail and Google Cloud Platform as entry points. At present, we only use GSuite for the use of Google Classroom. All email and other services are hosted on Office 365. When I configured GSuite, I disabled the use of Gmail, as I don't want any overlap or confusion between that and Office 365. Is there any other entry point/sign-on URL that can be configured? After a short chat with Google support, they said that the Gmail URL could be used even if Gmail was disabled globally, and that it would land the user on their Google account page. I proved this wrong just after leaving the chat - it states straightaway that email is disabled. I am aware that custom URLs can be created in GSuite, but from the looks of things on the Azure AD configuration side, it would appear that only Gmail or Cloud Platform strings can be used: Thanks.

What switch vendor/model are you using?

We have a variety of ProCurve switches within the building. We are currently preparing our network for a VoIP telephony system. I’ve noticed that around 50% of the switch models feature a variety of QoS options, compared to a ‘slimmed’ down offering of QoS options on the remainder of the switches. For example, our 2610, 2626 and 2650 models offer: - Application Type - Device Priority - Type Of Service - Protocol - VLAN priority - DSCP Policy Table - DiffServe TOS Whereas, our 2510, 2510G and 2510B models only offer; - Type Of Service - DSCP Policy Table - DiffServe TOS This is fine, as the 3 options above appear on all switches. In terms of setup for VoIP, all switches feature the ‘Voice VLAN’ option, which I have already enabled for the VLAN created for the phone network. From reading, I believe that enabling the Voice option for the VLAN will auto set the CoS priority to 7 – confirmation would be good? The 2510, 2510G and 2510B models support QoS, but don’t offer for the ‘Voice’ option to be enabled for the VLAN in the CLI. This is fine, as it can set the same parameters through the webmin. As the ‘DSCP Policy Table’ QoS option appears on all switches, this is what I would use. Q. Do I simply select the correct DSCP codepoint, and then set the 802.1p priority to 7? Thanks.

https://community.spiceworks.com/topic/1846854-cannot-route-between-vlans-on-an-hpe-1920-48g-poe

Timbo343, Davit2005 - thank you for your replies. Timbo343, hadn't thought about updating firmware - will grab the latest version. Davit2005 - need inter VLAN routing. It's almost as if 'ip routing' hasn't been run on the switch, but after seeing a few others mention the same thing regarding this particular model of switch, I read that routing is on by default. It's just strange that the routes aren't being created automatically, along with the internal loopback interfaces. Here's the current config: display current-configuration # version 5.20.99, Release 1112 # sysname CORE # domain default enable system # ipv6 # telnet server enable # ssl version ssl3.0 disable # password-recovery enable # vlan 1 # vlan 10 description Cygnets # domain system access-limit disable state active idle-cut disable self-service-url disable # user-group system group-attribute allow-guest # local-user admin password cipher $c$3$XCxJKTcIklnb9DlADGoG/R7tS4G/8BUPr2rlCmwBmwcp4Q== authorization-attribute level 3 service-type telnet terminal service-type web # stp mode rstp stp enable # interface NULL0 # interface Vlan-interface1 ip address 10.149.4.42 255.255.252.0 # interface Vlan-interface10 ipv6 address auto link-local ip address dhcp-alloc # interface GigabitEthernet1/0/1 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/2 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/3 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/4 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/5 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/6 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/7 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/8 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/9 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/10 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/11 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/12 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/13 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/14 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/15 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/16 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/17 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/18 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/19 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/20 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/21 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/22 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/23 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/24 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/25 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/26 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/27 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/28 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/29 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/30 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/31 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/32 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/33 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/34 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/35 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/36 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/37 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/38 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/39 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/40 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/41 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/42 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/43 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/44 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/45 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/46 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/48 port auto-power-down stp edged-port enable # interface GigabitEthernet1/0/49 stp edged-port enable # interface GigabitEthernet1/0/50 stp edged-port enable # interface GigabitEthernet1/0/51 stp edged-port enable # interface GigabitEthernet1/0/52 stp edged-port enable # ip route-static 192.168.1.0 255.255.255.0 Vlan-interface10 192.168.1.1 # undo info-center logfile enable # snmp-agent snmp-agent local-engineid 383030303633413236353133443839343033333343303736 snmp-agent sys-info contact Hewlett Packard Enterprise Company 3000 Hanover St Palo Alto, CA 94304 snmp-agent sys-info version v3 # load xml-configuration # user-interface aux 0 authentication-mode scheme user-interface vty 0 15 authentication-mode scheme From the commands available, I can't see a way to run an 'ip route x.x.x.x etc' or even to create a loopback interface. Here's a shot from a walkthrough for the switch - the routing for the newly created VLAN can be seen. Network ID of the new VLAN points to the chosen IP for the VLAN interface, which in turn points to the internal loopback of 127.0.0.1. Thanks chaps.

Address book policies are what you need to be looking for. Russian doll set-up with an address list within a new policy. You can then apply that policy against end users. Address Book Policy using Exchange Online (Office 365)

Anyone?

Hello there. Trying to setup a VLAN on the above switch. VLAN has been created, along with an IP for the VLAN interface. The issue I have is that I cannot ping the VLAN gateway IP. I need to know whether it's because nothing has been untagged for that VLAN, or whether something is awry with static routes. Now. When viewing the procedure for creating a new VLAN for this switch, I can see from screenshots that the appropriate static routes are automatically created for the new VLAN and it's respective interface IP in the 'IPv4 Routing' section. After creating my VLAN and the associated interface IP, the only entries in the routing section are for my default VLAN, and for the the 127.0.0.1 InLoopback0 interface. As the routes weren't being created automatically, I set about creating the routes manually. This too, resulted in failure, as when specifying 192.168.0.1 as the next hop for the 192.168.0.0 network, the switch informed me of an error: bad/invalid next hop address. I then found this - 3COm 4500 Inter Vlan routing newbie question - HP: A-Series networking solutions - Tek-Tips, after reading that this particular series of switch are based on older 3com devices. I switched the VLAN interface over to DHCP assignment and created the static route accordingly as follows: Dest IP: 192.168.1.0 Mask: 255.255.255.0 Next Hop: 192.168.1.1 Interface: Vlan-Interface10 Doing it this way allowed me to create the route, as mentioned in the link. However, I still need another static entry to route 192.168.1.1 (this will be the IP for the VLAN gateway), to 127.0.0.1. Attempting to do so presents me with another 'Error: Invalid next-hop address'. I should also mention that the initial static route is created successfully, but appears in the 'Summary' section of the 'IPv4 Routing' section, along with the default VLAN details, but instead remains in the 'Configured Static Route Information' section of the 'Create' tab. I all want to do is create a VLAN, assign it's GW IP, and be able to ping that gateway address from a PC in another VLAN. Do I have to ensure that a machine is first within the new VLAN before the ping will work? I ask as I have several VLANs configured on an HP Procurve 5300 series, and am able to ping the VLAN gateway regardless of assigning ports over to that new VLAN. Can anyone help?

Hello, Can anyone offer any real reviews on a decent USB 3.0 RAID enclosure? Simply after a 2-bay enclosure with RAID 1 capabilities. There do seem to be a few about, but to be honest the good majority look sub-standard, without even thinking about quality of the hardware inside. Have read a few good reports about this one - ICY DOCK MB662U3-2S Dual Bay USB 3.0 RAID Enclosure Any recommendations or real-world reviews welcomed. Thanks.

Can anyone recommend any malware protection for servers? I ask as there doesn't appear to be much on the subject, after Googling. Many thanks.

Office 2013 still seeing random crashes, even after installing the re-issued KB3097877, and after KB2975838 being installed. Hardware acceleration was already disabled prior to the issue.

Hello. Having a stab at getting an iPad to see an airplay-enabled Apple TV, on the same VLAN. As a test, there are no issues when placing both iPad and Apple TV on the default VLAN, through a wired or wireless connection. The iPad sees the Apple TV with no issue, and can mirror too. However, moving both onto a staff VLAN, results in the iPad not being able to see the Apple TV. Our wireless setup is Ruckus, with a ZoneDirector. Having looked at previous posts regarding setup of Bonjour Gateway on the ZD, it refers to using the BG as a sort of relay, for passing the apple traffic between VLANS. However, is this still relevant when both devices are on the same VLAN? Access points are linked to switch ports which have been set as trunk ports for all VLANs, with exception of the default VLAN which is untagged. Can anyone offer advice on how to proceed? Many thanks.

It is the free version of Backup and Replication.