C
CrazyDogTech
The single active NIC in my new Server 2012 R2 no longer shows the Network Location of "DOMAIN.LOCAL" like it did before I demoted the only Server 2003 domain controller. The NIC now shows "NETWORK" as the Network Location.
The registry still shows a Profile with the correct PROFILENAME in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
but that name does not show up in the Network List Manager Policies inside Local Security Policy.
The 2012 R2 Srv has all of the FSMO roles, Client PC's can connect to the domain but will not get new map drives from a script, they must be created manually. My Quickbooks Enterprise clients cannot see the QB Server Manager on this server and I think it is related to this issue because of firewall restrictions.
The Windows Firewall pointed me in this direction because the "Private Networks" is connected to my NIC named "Network" but the Firewall "Domain Networks" is reported as "Not connected."
Any Help is appreciated,
CrazyDog
Continue reading...
The registry still shows a Profile with the correct PROFILENAME in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
but that name does not show up in the Network List Manager Policies inside Local Security Policy.
The 2012 R2 Srv has all of the FSMO roles, Client PC's can connect to the domain but will not get new map drives from a script, they must be created manually. My Quickbooks Enterprise clients cannot see the QB Server Manager on this server and I think it is related to this issue because of firewall restrictions.
The Windows Firewall pointed me in this direction because the "Private Networks" is connected to my NIC named "Network" but the Firewall "Domain Networks" is reported as "Not connected."
Any Help is appreciated,
CrazyDog
Continue reading...