Install a new Domino 8.5.2 on Windows 2008 and not able to reach existing Domino server

Hi,

I’m running out of ideas and hope someone could give me some directions.

I have a Windows 2003 Domain Controller. I have installed my hub Domino server 8.0.2 FP3 (Server A) on this computer. Everything is working fine for many years.

Recently, I installed a Windows 2008 R2 64-bit server and joined to the Windows domain fine. I installed a Domino 8.5.2 (Server B) on this server and I can connect to the Domino server in the DC with no problem during installation.

When I try to issue the replicate command from the Server A to Server B, it errors out “The remote system is not responding”.

When I ping Server B from Server A, errors “Request timed out”.

When I ping Server A from Server B, I have no problem.

I thought it was IPV6 at fault, so I disabled it on Server B, however the issue still the same error.

I added TCP_EnableIPV6=1 to Notes.ini of both servers and still the same error.

I’m running out of ideas where went wrong. I hope to gather some ideas from this forum.

Could you help? Thanks…

Subject: os level configuration

not yet tried to use windows 2008.

but, if you can’t ping in os level, than the problem is not in lotus domino but in the os.

please try to fix the problem in the os first, if you can ping both ways, then lotus domino should connected without any problem.

can you provide the ip’s configuration for both servers and also the status of firewall?

Subject: Thanks Budi…

Thanks Budi.

I haven’t got a chance to go back and check the server as I was flooded with other requests.

Looking back the errors and server doc, I noticed one difference:

(1) If my Domino server is on Windows 2003, the Port after TCPIP will be named “NetBios”

(2) If my Domino server is on Windows 2008, the Port after TCPIP will be named “NetBios over TCP/IP Network”

I wonder if that’s the reason why I am seeing this in the Domino LOG.NSF:-

[LOG.NSF]

11/30/2010 12:25:57 PM LAN1tcpip: The network port driver is an incompatible version

I may try disable NetBIOS over TCP/IP by using DHCP server options:-

Link: Disable NetBIOS over TCP/IP by using DHCP - Windows Server | Microsoft Learn

Will post back later…

Subject: Check firewall

Have you opened up port 1352 in the Windows firewall?

Subject: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

I always have this error on Server B in the Domino console log:-

11/30/2010 12:25:57 PM LAN1tcpip: The network port driver is an incompatible version

I have since disabled the port “NetBios over TCP/IP Network” but I still cannot trace Server B from Server A’s Domino console.

[Domino LOG]

11/30/2010 12:29:38 PM Network: Determining path to server Server-B

11/30/2010 12:29:38 PM Network: Available Ports: TCPIP

11/30/2010 12:29:38 PM Network: Checking normal priority connection documents only…

11/30/2010 12:29:38 PM Network: Allowing wild card connection documents…

11/30/2010 12:29:38 PM Network: Enabling name service requests and probes…

11/30/2010 12:29:38 PM Network: Address found in local TCPIP names table for Server-B

11/30/2010 12:29:38 PM Network: Connecting to Server-B over TCPIP

11/30/2010 12:29:38 PM Network: Using address ‘Server-B.mynetwork.net’ for Server-B on TCPIP

11/30/2010 12:29:38 PM Network: Requesting IP Address for Server-B.mynetwork.net from DNS

11/30/2010 12:29:38 PM Network: DNS returned address 10.200.128.196 for Server-B.mynetwork.net

11/30/2010 12:29:43 PM Network: Unable to connect to Server-B on TCPIP (The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.)

11/30/2010 12:29:43 PM Error connecting to server Server-B: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

Subject: It’s the Windows Firewall

Add Firewall exceptions as follows…1. Start the Windows Server 2008 Server Manager program.

  1. Go to Configuration → Windows Firewall → Inbound Rules → New Rule.

  2. Set Type = Port, TCP/UDP = TCP, Specific Port = 1352, Allow the Connection, When = Domain+Private+Public (or set as you want for tighter security), Name = Lotus Notes. If your server is also a domino web server then you will need to open port 80 also.

  3. Press Finish to save and enable the new rule.

  4. Find the built-in rule named “File and Printer Sharing Echo Request ICMPv4”. Enable this rule. (This step is not required but it allows the server to respond to a standard PING request, which is often helpful.)

Hope that helps.

Michael

Subject: Thanks for your detail posting, Michael.

Thanks for your detail posting, Michael. I will give it a try tomorrow when I return office and will post here for an update. :slight_smile:

Subject: It worked and Windows 2008 Firewall is the cause.

Thanks Nephrops Norvegicus or Michael. Really appreciate your posting with the resolution!

Subject: BTW, for test ENV, simply disable Windows firewall.

FYI.