Disk2VHD/SQLServer
-
@marcinozga is more than likely correct, because there are new drivers for the new underlying hardware the OS did a system check and said "oh wait a minute... new firewall rule here" and that was causing the issue.
But everything else would be identical up to the point of a system check, where the OS found new hardware.
-
It seems weird to me that the driver would have anything to do with it, but I do agree that the Network Profile is like different - i.e. The server thinks it's on a public network now instead of a domain or private network, so the firewall settings changed to match the new network profile.
-
@dashrender said in Disk2VHD/SQLServer:
It seems weird to me that the driver would have anything to do with it, but I do agree that the Network Profile is like different - i.e. The server thinks it's on a public network now instead of a domain or private network, so the firewall settings changed to match the new network profile.
Why would this be weird? Every time you change the network card you get new adapters. That is how windows has always worked.
-
The network adapter of the VM is joined to the domain network, so its not seeing its self as public/private. Its seeing its self as domain, which is it and was. Same network.
Its a rough direction though, so thanks
Edit - to add 'not' -
@jaredbusch said in Disk2VHD/SQLServer:
@dashrender said in Disk2VHD/SQLServer:
It seems weird to me that the driver would have anything to do with it, but I do agree that the Network Profile is like different - i.e. The server thinks it's on a public network now instead of a domain or private network, so the firewall settings changed to match the new network profile.
Why would this be weird? Every time you change the network card you get new adapters. That is how windows has always worked.
I see, but... the new adapter (inc drivers) are still joined to the same LAN. The connection identified as domain connection. So, the firewall set of rules under 'domain' would still apply right? Regardless of what adapter is used...
-
Reboot the server, that usually fixes network profile assignment.
-
@marcinozga said in Disk2VHD/SQLServer:
Reboot the server, that usually fixes network profile assignment.
That's not the issue. Like I said, the profile sees its self as domain. NOT private/public. Its domain.
-
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
Reboot the server, that usually fixes network profile assignment.
That's not the issue. Like I said, the profile sees its self as domain. NOT private/public. Its domain.
I would still reboot. It's Windows after all.
-
@marcinozga said in Disk2VHD/SQLServer:
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
Reboot the server, that usually fixes network profile assignment.
That's not the issue. Like I said, the profile sees its self as domain. NOT private/public. Its domain.
I would still reboot. It's Windows after all.
I shall tonight and try. We are just running it at the moment with domain firewall off, so SSMS works for the devs. Will turn domain on, restart, and see tonight... but even so, it is domain network as identified.
-
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
Reboot the server, that usually fixes network profile assignment.
That's not the issue. Like I said, the profile sees its self as domain. NOT private/public. Its domain.
I would still reboot. It's Windows after all.
I shall tonight and try. We are just running it at the moment with domain firewall off, so SSMS works for the devs. Will turn domain on, restart, and see tonight... but even so, it is domain network as identified.
Did you look at the firewall setting themselves to see if they are set as desired?
-
@dashrender said in Disk2VHD/SQLServer:
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
@jimmy9008 said in Disk2VHD/SQLServer:
@marcinozga said in Disk2VHD/SQLServer:
Reboot the server, that usually fixes network profile assignment.
That's not the issue. Like I said, the profile sees its self as domain. NOT private/public. Its domain.
I would still reboot. It's Windows after all.
I shall tonight and try. We are just running it at the moment with domain firewall off, so SSMS works for the devs. Will turn domain on, restart, and see tonight... but even so, it is domain network as identified.
Did you look at the firewall setting themselves to see if they are set as desired?
Not yet. Its not been looked at. I will turn the old physical box on to compare. (Obviously disconnected from the network entirely).
Not sure why Disk2VHD could have 'broke' the domain firewall rules.
-
You can just export the firewall rules from your physical box and then import it to your virtual machine.
Using group policy also makes managing the firewall rules a lot easier too.
-
@black3dynamite said in Disk2VHD/SQLServer:
You can just export the firewall rules from your physical box and then import it to your virtual machine.
Using group policy also makes managing the firewall rules a lot easier too.
I'd like to see if they are different before making any changes. As I understand, disk2vhd should not have changed these... so, I should need to change the rule. They should have been as they were on the physical machine... right? So will compare them.
-
@jaredbusch said in Disk2VHD/SQLServer:
@dashrender said in Disk2VHD/SQLServer:
It seems weird to me that the driver would have anything to do with it, but I do agree that the Network Profile is like different - i.e. The server thinks it's on a public network now instead of a domain or private network, so the firewall settings changed to match the new network profile.
Why would this be weird? Every time you change the network card you get new adapters. That is how windows has always worked.
What's weird is (was) that simply a new NIC would cause this issue. That's all I was saying. If the new NIC came up on the Domain Network Profile, you would assume all would stay the same. It's not weird that a new NIC would come up on a different Network Profile, i.e. prehaps it didn't detect the network link correctly - I've seen this many times.
