Advertisements

Category: Windows Server



Hello All, It’s time for a little Biz Talk…

BizTalk Internal Error

Gone through this error recently and I wanted to blog this so that users who might face this kind of issue are relieved. From the above error; what’s the main issue cause cannot be so easily guessable or displayed for quick resolution approach for a system admin. The primary cause for this kind of error is name resolution between BizTalk and SQL servers. We have to ensure that the name resolution is proper between Web/BizTalk and SQL servers. Check the ping results from Web to SQL for FQDN (Fully Qualified Domain Name; example.test.com) and DNS Name only(example) of the SQL server, and be assured that proper reach of the right server is seen in this case. And ensure in the NIC settings of SQL server that DNS suffix is not specified particularly to any other domains, or  for safe side the domain this SQL server resides can be mentioned, however not required when auto register option is selected.

DNS Suffix Settings

For this settings to check, Go to Network Connections; which can be opened via NCPA.CPL command and then open the Network Interface which is the connection interface between WEB and SQL nodes talk and then Go to properties of the Ethernet adapter and click on TCP/IP 4 version and click on properties again to have this accessed.

2 4

6

Then Ensure the above tick boxes are there for this NIC to have a proper name resolution in the network.

This must solve the case of name resolution between nodes for proper communication. Reach me out if you have any queries regarding this case.

 

Cheers!

Chaladi

Advertisements

Background:

I faced this issue a year ago and now just realized that there can be guys out there struggling/looking for the solution. Basically the problem is: We are not able to reach any Terminal/Remote Apps hosted on our Terminal/Remote App Server or any services are explicitly failing to reach via network.

Note: This applies to Problems with Firewall getting  disabled by GPOs automatically.

Situation 1:

Well, that basically narrows down us to Firewall, but even if we enabled/Disabled firewall with Rules defined, the applications are not getting connected or Remote desktop fails too.

Situation 2:

We see that Firewall is getting disabled or enabled as per Domain GPO Policy and for this we were not getting succeeded even if the firewall rules were defined, but able to get through firewall for sometime after the firewall is enabled/disabled manually on the server.

Resolution:

For this kinda problem we are very sure that Firewall is to be blamed here, but we have put our efforts on Firewall and still not getting us through because of GPO policies. The solution is to look at the Firewall policies Profiles that’s defined on the server:

We have to configure Firewall Profiles that will explicitly coordinate with the GPOs. For this you have to configure Windows firewall from SECPOL.MSC or WF.MSC and configure the Windows Profiles as below listed.

 

For the Organisation, since it would have Domain Network and possibility of Private you can configure these both profiles, and if your Organisation has Public network configured configure the same as well.

WINDOWS-FIREWALL

You configure Domain, Public and Private Profiles and enable Traffic to flow through Firewall enabled for Inbound and Outbound connections. You do the same for three profiles and say it okay, as per requirements. Now even if the Domain GPO forces this server to get the Firewall disabled, the applications and services can be reached out without any problems.

 

This applies to Problems where Firewall is getting  disabled by GPOs.

 

 

 

%d bloggers like this: