wessir
asked on
SQL Server rule in Advanced Firewall Rule only works if using 'Public' profile in a domain environment
SQL2K8R2 server host W2K8 std is a domain member. SQL server manager is on a WindowsXP workstation also a domain member. Port 1433 firewall rule only allows connection if the 'public' firewall profile is checked. Doesn't work if just the 'Domain' or 'Private' profiles.
Shouldn't two computers joined to the same domain work in the 'Domain' profile for the Advanced Firewall inbound rule? How do I troubleshoot this or am I not understanding the difference between the three profiles correctly?
Shouldn't two computers joined to the same domain work in the 'Domain' profile for the Advanced Firewall inbound rule? How do I troubleshoot this or am I not understanding the difference between the three profiles correctly?
ASKER
It has multiple NICS as well as Hyper-V virtual networks. The SQL server is listening on 10.20.0.29 The network connection associated with that IP is showing the domain name under it. But I believe the machine was joined to the domain using a different network connection and that network connection is showing 'Unidentified network' under it.
I think you hit it with your answer, is there an easy way to change this?
I think you hit it with your answer, is there an easy way to change this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, I see what happened there. Good catch.
Basically, if the server is authenticated to a DC over a certain adapter, that adapter is placed in the Domain profile. No choice.
But this thread appears to mention a specific problem with Broadcom teaming adapters, with a solution:
http://community.spiceworks.com/topic/85898