Network Protocols and Ports Requirement

Which TCP/IP Port Numbers Are Used by Imorgon?
What Exceptions Do I need to Create in Microsoft Firewall

For Workstations

  • Microsoft Remote Terminal 3389
  • SQL Manager/Debug Port 135 (Note that Microsoft Firewall Cannot Block This Port)
  • SQL Browser: Port 1434 (UDP only): [Note this is optional, if you cannot allow 1434, please let us know to use port number instead of instance name in connections]
  • SQL Data (Imorgon Instance, Specially Configured): 3441
  • Port 80: Used by Imorgon Web (May be blocked if HTPPS only is used)
  • DICOM: 104
  • Port 443: HTTPS for Imorgon Web Viewer
  • Port 1234: Used by Imorgon Agent
  • Port 5900: Used by VNC Viewer
  • Port 5800: Used by VNC Viewer

For Servers

  • Microsoft Remote Terminal 3389
  • SQL Imorgon Instance Uses Dynamic Ports See below to find out which number it is.
  • SQL Mirroring Port 5022
  • SQL Manager/Debug Port 135 (Note that Microsoft Firewall Cannot Block This Port)
  • SQL Browser: Port 1434 (UDP only): (Note this is optional, if you cannot allow 1434, please let us know to use port number instead of instance name in connections).
  • SQL Data (Imorgon Instance, Specially Configured): 3441
  • Port 80: Used by Imorgon Web (May be blocked if HTPPS only is used)
  • DICOM: 104
  • Active Directory Authentication: 445 TCP & UDP) and 464 (TCP)
  • Port 443: HTTPS for Imorgon Web Viewer
  • Port 1234: Used by Imorgon Agent
  • Port 5900: Used by VNC Viewer
  • Port 5800: Used by VNC Viewer
  • Port 6661: HL7 Incoming Traffic Default Mirth Port.
  • Also Allow sqlsrvr.exe exeption to the IMORGON instance. This is typically in
    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe  But it can be at a different location if there are other SQL instances installed previously or running concurrently.

Discovering and/or Fixing the SQL Imorgon Instance Port Number (Dynamically Assigned)


  1. From the Start menu, Go to "Microsoft SQL Server 2005", "Configuration Tools" and open "SQL Server Configuration Manager"
  2. From the SQL Server Configuration Manager on the left panel, find SQL Server 2005 Network Configuration. Click to reveal additional configurations inside this "tree."
  3. Find Protocols for Imorgon. Click it, and all supported protocols will appear on the right.
  4. Be sure that TCP/IP is enabled.
  5. Click the TCP/IP protocol icon to reveal its configuration.
  6. Select the "IP Address" Tab.
  7. Scroll all the way down to this dialogbox, you will find IPAll section. Check in "TCP Dynamic Ports" and read off the port number. This is the port number that Imorgon SQL Instance listens to. To fix this port number to something consistent blank out the Dynamic port number and type in our default choice of 3441 there and restart the SQL service. Telnet to the port 3441 remotely to make sure that it is now active.

How To Diagnose the SQL Browser Port Blocking Issue

To diagnose if the SQL browser port is being blocked, you can use Microsoft ODBC configuration to test this. Please also know the port number of the Imorgon Instance as described above.

  1. Go to Control Panel: Administrative Tools.
  2. Open Data Sources (ODBC)
  3. Under the User DSN tab, press "Add..."
  4. Under the Create New Data Source window, scroll all the way down and select SQL Server. Press Finish.
  5. Under the Create a New Data Source to SQL Server window type in IMORGON in the name field, Imorgon Test in the Description Field and type in the name or the IP address of the Imorgon principal server a \ and IMORGON (e.g. IMSERVER\IMORGON) in the Server field.
  6. Press Next
  7. Select "With SQL server authentication using a login ID and password entered by the user."
  8. In the Login ID field type in sa
  9. In the Password filed type in searidge2 (or appropriate password)
  10. If at this point the screen goes to the next page (with Change the default database field) right away then it can find the instance using the SQL Browser. If it hangs, you have either forgotten to type in the "\IMORGON" in the server field of the first screen, or the SQL Browser is blocked.
  11. To make sure that actual SQL Connection works, go to the first page where you typed in the Server and instance name and specify the port number directly. To do this you type in the Sever name, a comma, and the port without leaving any space. For example instead of of typing in IMSERVER\IMORGON, you would type in IMSERVER,3411 provided that the server instance is using the port 3411.


UDP Port 1434 Blocked Issue: Microsoft Detection Tool


Blocking of port 1434


It is not uncommon for UDP traffic on port 1434 to be blocked for security reasons. When this is the case, SQL Browser does not return the dynamic port number and static ports should be used instead.

Troubleshooting can be difficult depending on where UDP 1434 is blocked. If blocking is done at the router between subnets, SQL Browser will work if the remote machine is on the same subnet, but not if it is across the router boundary on another subnet.

Microsoft has a free tool called PortQry for troubleshooting ports. It is available for download fromhttp://www.microsoft.com/downloads/details.aspx?FamilyID=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=en. Run PortQry from a command prompt using syntax similar to this:

portqry -n ipAddressOrMachineName -e 1434 -p UDP

If 1434 is blocked, the last line returned from PortQry looks like this:

UDP port 1434 (ms-sql-m service): FILTERED

If a static port is assigned to a named instance, a client alias can be used instead of putting the static port number into connection strings.

TCP Port 135 Block Issue For SQL Server Management Studio Accessing "Other" Server

 
If the port 135 is blocked and if you try to use Microsoft SQL Server Management Studio, you will get the following error message. SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified.
 
 

 
Comments