Posts made by i3

I have an MS Server 2012 R2 with a usb 3.0 disk attached for nightly full image backup using Windows Backup. It has started to complete with warnings, quoting there are 4096 bytes that are unreadable. I have done multiple checkdisk /r and rebooted the machine but the backup still fails to complete. The current OS is on a pair of 1TB WD Red's in a RAID 1 (Intel Raid). I am attempting to image the entire machine and install 4 new WD Gold's in a Raid 10 configuration.

I also installed Veeam Endpoint and tried to do a full image but that fails with a different error. I reached out to Veeam support and they tried a few things but were unable to assist.

Any ideas or would the best plan of action at this point to install Hyper-V server on the new Raid 10, and disk to vhd the old server and run it virtually?

@ccwtech Is it the initial launch of the application that is slow or the navigation within the application? I assume this behavior happens on every computer? Are they all hardwired or wireless? Can you run an extended ping (ping -t) to the application server from a computer having the issues and make note what the response times are after hours vs. during hours. If you attempt to copy some files from the same UNC path the main exe is at to a temp folder on the local pc, what kind of file transfer speeds are you seeing?

@hobbit666 said in Installing Hyper-V 2016:

at HQ all on the same domain etc so I reinstall on KVM (XenServer at least)

It has been a while since I was testing this in a workgroup environment, but I had this link in my notes.
http://pc-addicts.com/12-steps-to-remotely-manage-hyper-v-server-2012-core/

@jaredbusch
Are you creating vlans on the ERL?

@dashrender said in VLAN question:

If the router has switch ability built in, then the router might allow VLAN1 traffic on all ports of the switch. You don't seem to want this, so you should disable the switch feature, if the router has this feature.

Correct, that has already been turned off or blocked on the port going to floor 2, keeping the 2nd floor isolated.

@dashrender said in VLAN question:

So this is failover only? You're not routing traffic for floor 1 out ISP 1 and floor 2 out ISP 2, right?

The 2nd floor does not rely on the internet as much as the 1st floor. The 1st floor has it's main internet connection and uses the 2nd internet as a backup in the event that their's goes down. Floor 2 uses the 2nd internet connection as it's main isp. This is all handled by the firewall.

Everything is working as designed and the two floors are separated, my only sticking point is that the 2nd floor switch (EdgeSwtich) has its default vlan (vlan1) as the 172.16.0.0 network but on the 1st floor and the firewall the default vlan is the 192.168.1.0 network. While I understand how this is setup now, is there a better way of configuring it.

Two ISP's for failover. We utilize quite a few different cloud services, with hosted phones being one of them.

@dashrender said in VLAN question:

" Considering that you say that zero traffic from Floor 1 should interact with traffic on Floor 2, why does it matter if things match across the whole site?"

To make it easier to visualize and understand for anyone other than me.

@dashrender said in VLAN question:

Scott just mentioned that he believes that the Meraki might have a switch feature in it's router. If that's the case, and you're not using it, why not disable it.

I am not sure I understand this.

We are using one firewall to take advantage of ISP failover in the event the primary goes down the first floor will failover and use the 2nd floor's internet connection.

I omitted the 2nd internet connection but yes we have two. Floor 2 uses the second connection to the internet and floor 1 the primary connection. The guest network cannot be the same for both floors. I do require wired access to only vlan 1 on floor 1 and vlan 3 on floor 2.

Sorry, the separation of floors is due to a subentity of the main company.

To provide both a secure and guest wifi access using the same access points across the floors.

Would there be a better way to configure this setup so that the vlans on the 2nd floor switch match across the entire site? I was thinking to set all ports, except the trunk port, on the 2nd floor switch to untagged for vlan 3, and excluding vlan 1 and vlan 2 from all ports on the same switch.

I have a Meraki firewall configured with 4 VLANs.
VLAN 1 - default 192.168.1.0/24
VLAN 2 - guest 192.168.2.0/24
VLAN 3 - 2nd floor 172.16.0.0/23
VLAN 4 - 2nd fl guest 172.17.0.0/23

I am separating out two floors, floor 1 will get VLANs 1 and 2 and floor 2 will get 3 and 4. No communication needs to happen across any of the vlans. The port on the firewall connecting to the first-floor switch is a trunk port on the native VLAN allowing VLANs 1 and 2. The port on the firewall connection to the 2nd-floor switch is also a trunk port allowing VLANs 3 and 4 with 3 being the native VLAN on that port. Because of this, when I configure the VLAN on the switch on floor 2, I currently have VLAN 1 (default), VLAN 3 and VLAN 4, however, VLAN 1 is actually the 172.16.0.0 network. Everything works and I am able to have the guest wifi (VLAN 4) issue from the ap's, however it is a bit confusing as the default VLAN on the switch on floor 2 is actually VLAN 3 on the firewall.

@RojoLoco That's what I was leaning towards. It's a coincidence that the ProSupport expires in a few weeks and that the tech had mentioned it as soon as we were connected.

I had an older version of Dell OpenManage Server installed under Storage > Physical disks there was a column for Predicted Failure. All drives showed yes. Server is working fine and dual backups are successful each day. I contacted Dell and they first said to update the Open Manage Server software which I did. Now the new version does not have the Predicted Failure column at all. The tech is telling me that the new version will show you if you have a Predicted Failure but if you don't it will hide the column. Anyone run into anthing like this? Dell R210 Perc H200.

I believe you can't manage Hyper-V Server 2016 from Windows 7. Someone correct me if I am wrong, but I think you need Windows 10 to do so. Also, if you trying to connect to the Hyper-V host using the "Connect as user" option in the "Connect to Server dialog box", I also had issues with that, I had to log into the client pc as the same user I was attempting to connect to the Hyper-V server as.

@wirestyle22 said in Hyper-V Manager Unable to connect to Hyper-V Host from Remote Workstation:

his is a new install

What OS is the Hyper-V server running?

Is the user you are logged into Windows 7 have the rights to manage the new Hyper-V server?

The Hyper-V server you are attempting to manage, is it a full GUI with Hyper-V role or just a Hyper-V server?

Are both machines in the same domain? Has this worked in the past? Does the user you are logged in as have permissions on the Hyper-V host? What is the client os you are using Hyper-V Manager from?

@dafyre Also in the NIC driver properties? Yes, but only on the NIC 2 dedicated to the virtual guest network, not the host NIC.

@Dashrender I did update the NIC driver. It is a Dell Server with Broadcom NetXtreme Gigabit NICs. It originally shipped with a 16.0 driver version, I updated to 17.4 from Dell's site. Rebooted and still the issue is the same. I even read an article about the same issue and trying to disable TCP/UDP Checksum Offload in the NIC driver properties. The machine is currently not in production so I tried it, but it didn't make a difference. However I only did that on the NIC 2 that is dedicated to the virtual guest network not the host NIC.

@Dashrender No it does not. I have a constant ping running to it from the host, as well as a constant ping from within the vm to our gateway and neither drop any packets. Response time is usually 1ms.

I can rdp into the guest and maintain a constant connection without any drops at all.