Network setup - Hyper-V
-
@scottalanmiller said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@scottalanmiller said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
This is a bit like old school Quickbooks from the sounds of it. No real DB interface, instead it's just an exe that's being pulled across the network, executed on the PC, then the data is also pulled over that same network connection.
In the case of RDS, everything is local, no network involvement at all, so any performance issues cause by the network overhead are gone.
I'd expect RDS to use SMB just the same as any other end point.
In the case of the OP, the application is in a folder on the RDS server. so no SMB needed.
A test would be accessing it via the share instead of via the local drive letter.
You can not use a drive letter with the software (according to the software vendor) - it's all via unc path.
So weird, the drive letter is just a perm UNC mapping.
I am aware, but if they see a drive mapped their support will walk away... To quote myself "You remember which software you are talking about."
-
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
-
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
-
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
-
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
Remind me - Hyper-V 2016? RDS on Window Server 2016?
-
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
Is it slow for PC (SMB Share) users right now?
-
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
Remind me - Hyper-V 2016? RDS on Window Server 2016?
Yes
-
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
Is it slow for PC (SMB Share) users right now?
Yes
-
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
Is it slow for PC (SMB Share) users right now?
That's odd. That means that either it is not loading into memory or the PCs themselves are what is slow.
-
Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.
The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.
Requirements:
Processor Intel
Core i7, i5, i3 Intel Core 
2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 Professional -
@ccwtech said in Network setup - Hyper-V:
Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.
The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.
Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 ProfessionalYou can try setting up a Windows 10, 8.1 and 7 VM on the host and see if the performance is still slow.
-
@black3dynamite said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.
The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.
Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 ProfessionalYou can try setting up a Windows 10, 8.1 and 7 VM on the host and see if the performance is still slow.
I can try that, but how would that be different than running it on the other VM (Server 2016) that is the DC?
-
@ccwtech said in Network setup - Hyper-V:
@black3dynamite said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.
The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.
Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 ProfessionalYou can try setting up a Windows 10, 8.1 and 7 VM on the host and see if the performance is still slow.
I can try that, but how would that be different than running it on the other VM (Server 2016) that is the DC?
Well if its still slow when trying to access the application from the DC too then never mind my previous response. Just wondering if its a hardware or driver issue on those workstations.
-
That's the $1,000,000 question...
-
It would not hurt to set up a Windows workstation as a VM and do a test to make sure that you’re not having some kind of problem with that Windows server vm
-
@dashrender said in Network setup - Hyper-V:
It would not hurt to set up a Windows workstation as a VM and do a test to make sure that you’re not having some kind of problem with that Windows server vm
I'm willing to try almost anything right now. I just was wondering what that would show... Booting up a VM shortly.
-
@dashrender I have set up another VM (In this case Windows 7 Pro 64 bit with SP1)
It's slow on this machine as well.
Anything outside of the VM where this app runs is slow (virtual or physical machines).
I haven't enabled SMB 1, does that need to be done on the VM and Physical machine?
-
Ideally you'd want to use the very latest SMB protocol. But that doesn't appear to be the issue regardless.
-
@scottalanmiller said in Network setup - Hyper-V:
Ideally you'd want to use the very latest SMB protocol. But that doesn't appear to be the issue regardless.
Ok, it had been suggested here.
I'm just looking for anything else to try at this point.
-
Maybe there is a DNS issue and things are stalling on resolution?
