Thursday, February 14, 2013 2:24 PM
Did my reading and to me it appears only the following SQL ports need to be open 1433 (TCP/UDP) and 1434 (TCP/UDP). I have also created a couple 'Inbound' FW rules for the 'sqlsrvr.exe' and the 'sqlbrowser.exe to allow MDT and SQL to co-exist.
Our networking team are being pains telling me it has to be something with my config.
When I am on my subnet (192.168.96.0/24) everything works. My test MDT/SQL Xpress R2 server is also located on this subnet (installed on same server). When I go to a different subnet (i.e. 192.168.7.0/24) I am able to boot off my WinPE and it displays all my TS's (so I know it is connecting to MDT), but it doesn't read my custom settings from the SQL DB.
To me it seems there is something blocking SQL traffic?!? or is there seeing that MDT 2012 and SQL are installed/configured on the same server.
Thursday, February 14, 2013 4:04 PM
What is the difference between TCP/IP vs. Named Pipes and is one better than the other? If MDT/WDS/ and SQL are installed on the same server is there one that should be used over the other?
- Marked As Answer by ZoeTaite Wednesday, February 27, 2013 8:45 PM
Thursday, February 14, 2013 8:43 PM
Found the following. Does this make any sense to anyone who has used SQL 2008 Express R2:Error: "-2147467259 [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access de
<h3 ?>ResolutionRemove the NetBios name of the SQL Server from the text file in the 'Process Servers listed in this file' section of the SQL Processing Wizard, then add the IP address that was validated as the SQL Server to process.
Ultimately, this is a network issue that needs to be resolved, and this is considered a workaround for the tool to process the SQL Server