InstallAware

We are seeing issues when testing a connection to MS SQL Server before we attempt to run Scripts. The quote below states the results of the diagnosis. Please comment on the use of NetBios in the Plug-In and if the Plug-In does use NetBios what can you suggest as a workaround for those Clients who choose to disable NetBios to harden their servers.

"I spoke with the guys from [OUR CLIENT] today, who have been having problems with the DM installer connecting to their SQL server.

The normal SQL connection failure support testing diagnosis starts by trying ODBC (which worked) because it usually points to permissions or the firewall.

ODBC worked but the installer didn't. The customer went beyond this to try a sample app that used OLEDB. It also worked.

Their next step was to pursue it via Wireshark, which is how they discovered that IA was attempting to connect via NetBios.

I am not sure if IA can be instructed not to use NetBios, or not to use it first, but it is hard not to wonder if this is the source of a good portion of the connection issues we have during the install.

For some time, disabling NetBios has been a fairly common thing when hardening a server, which is why I think we're seeing this more on DM customers than we did on PPP (bigger biz, more likely to have a real IT staff)."

Dear StevePro,

honestly, I suppose the error is somewhere else.
I never enabled NETBIOS on my test machines.

If you can send my a very minimal sample that demonstrates your issue, I will have a look.

Regards

I may be mistaken but NetBios over TCP/IP is enabled by default on a windows box

https://support.powerdnn.com/KB/a545/te ... tbios.aspx

Dear StevePro,

please excuse me, I confused the NetBios settings of the net card adapter with the TCP NetBios you are referring to.

Let me verify it.

Regards

FrancescoT wrote:Dear StevePro,

please excuse me, I confused the NetBios settings of the net card adapter with the TCP NetBios you are referring to.

Let me verify it.

Regards

I have no answer on this!. "Does the SQL Plug-In use NetBios to connect to SQL Server"? Should be a simple question to the development department.

Another issue with another client with hardened servers. Thread Below.


[9:54:59 AM] WBI - Teresa: Having issues with [OUR IA INSTALLER] connecting to SQL Server [AT CLIENT LOCATION]
[9:55:16 AM] WBI - Teresa: They have a separate SQL Server Database Server
[9:55:17 AM] Mark: DM or PPP?
[9:55:20 AM] WBI - Teresa: DM
[9:55:32 AM] Mark: assume its 2008 R2 or later:)
[9:55:40 AM] WBI - Teresa: 2008 R2
[9:55:42 AM] Mark: wonder if its the netbios issue.
[9:56:05 AM] Mark: installer is using netbios to attempt to connect - most hardened servers have it disabled (netbios over tcpip)
[9:56:33 AM] WBI - Teresa: quite possible
[9:56:46 AM] WBI - Teresa: we can connect to the sql server via ODBC
[9:57:15 AM] WBI - Teresa: When it goes through the search in the DM Install, it comes up with no databases
[9:58:01 AM] WBI - Teresa: so if netbios was disabled, may be a symptom
[9:58:09 AM] Mark: ODBC - yeah, that happened for the people i was working with too.
[9:58:30 AM] Mark: The customer actually had IT people and they figured it out.
[9:58:43 AM] Mark: Theres a setting in TCPIP properties to enable/disable netbios over tcpip.
[9:58:55 AM] WBI - Teresa: they are on different subnets....
[9:59:00 AM] Mark: I suspect their security people wont be happy about turning that on if its off.
[9:59:01 AM] WBI - Teresa: they are in level 3 network
[9:59:13 AM] Mark: i am not sure if netbios is routable.
[9:59:20 AM] WBI - Teresa: no, it's not
[9:59:29 AM] Mark: even over tcp.
[9:59:38 AM] WBI - Teresa: that's the response from them when I asked them if netbios was off
[9:59:41 AM] Mark: anyhow, i would look there first

Dear StevePro,

Yes, I checked it and the answer is that our plugin doesn't require Netbios enabled.

For you convenience, following you can read the complete answer I received from our developent team, as answer to your question and to this other one (http://www.installaware.com/forum/viewtopic.php?f=2&t=9625&p=35501#p35501) as well.

138 and 445 are file and print sharing ports and can be closed. They may not be related to SQL server. Usually SQL server listens on 1433 unless set up to the contrary. SQL server connections can and do happen even with SMB/NetBios disabled. In fact some suggest disabling SMB/NetBios to increase security on SQL server installations. I've heard in cluster structures, with NetBios off, nodes can have problems seeing each other; but that's not what we're looking at here.

Our plug-in uses the MS SQL Native Client mechanism; so we don’t need any baggage for the SQL connections.

I suspect the situation is related to the SQL server setup. If "named pipes over NetBios" are enabled then port 445 is needed. In that case NetBios also needs to be on, file/print sharing ports must be activated; the firewall closes these typically.

More information: http://support.microsoft.com/kb/839269

NOTE!
I have not forgotten your question, but you are not the only one that asks for an answer ... and each one receives always a response.

Regards

Thank you for the speedy response. If we find out, I will post why this client is having issues for the benefit of other users.