A Great Deal Of Data Is Required By Support

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

Hi Rajveeken,

Here are the steps that need to be taken when you receive the TCP/IP Protocol Errors on the Domino Server. 99% of the time the issue lies outside of Domino and can be caused by 3rd Party Software, Network Card drivers/Hardware, or OS Page File and the chance Domino. The reason I mention this is when Domino is shutdown it releases all of the ports it uses and with a restart of Domino you still have the issue with the end result requiring a reboot of the OS. If this is the behavior you are seeing and an OS reboot is required Domino can pretty much be ruled out.

NOTE: Prior to following the steps outlined below, at the next occurrence of the issue, restart Domino (not the Entire OS). If the issue is still occurring when you bring Domino back up, then you can rule Domino out as the cause of the issue. However, the steps outlined below (especially the Netstats) will aid you in determining what is causing the issue.

In order for IBM to troubleshoot this issue, you need to enable the following debug on your server and follow the steps below, this is important if you do have an outage in the future. It is also recommended to verify the network card has the latest driver or similar driver as your other servers that are not having an issue:

From the Server Console:

Set Config Debug_threadid=1 --->Takes effect immediately
Set Config Console_log_enabled=1 --->Takes effect immediately

If the Server generates the TCP/IP error, hangs or is slow, open a command prompt on the Domino Server:

1.) When the server generates the TCP error, hangs or stops responding , check if the domino console is responsive , if it is , then run the following commands

show stat

show tasks

show server

show users

2.)
RDP into the Server using the console Switch:

Start-->Run-->mstsc -console or Start-->Run-->mstsc -admin (If you have the newest Version of RDP, Note you should see the server console)

Once connected to the server open a command prompt:

Win2000: Issue a netstat -an > C:\netstat1.txt
Win2003: Issue a netstat -abn > C:\netstat1.txt

3.)
Now open another command prompt:

Start-->Run-->cmd

Once the command prompt is opened we need to change directories from the C: drive to your data drive which is example D:\ so we issue the following:
D:

Now that we have changed directories to the D:\ drive we need to make sure we path out to the data folder

cd\notes\data

Now we are in the data folder and need to path to the Domino directory to run the manual NSD:

c:\notes\nsd -detach

I have included Technote 1204263 below as well, which outlines this process:

Lotus Software Knowledge Base Document

Title: How to run a manual NSD for Notes/Domino on Windows
Doc #: 1204263
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21204263

4.)
Once the NSD is completed open a command prompt or go back to the original cmd prompt for netstat and issue the following command again:

Win2000: Issue a netstat -an > C:\netstat2.txt
Win2003: Issue a netstat -abn > C:\netstat2.txt

5.)
Collect another NSD using the steps from Step 3

6.)
Once the NSD is completed open a command prompt or go back to the original cmd prompt for netstat and issue the following command again:

Win2000: Issue a netstat -an > C:\netstat3.txt
Win2003: Issue a netstat -abn > C:\netstat3.txt

7.)Bring down the Domino Server

Win2000: Issue a netstat -an > C:\netstat4.txt
Win2003: Issue a netstat -abn > C:\netstat4.txt

8.)Restart the Domino Server without rebooting the OS can you connect?

Win2000: Issue a netstat -an > C:\netstat5.txt
Win2003: Issue a netstat -abn > C:\netstat5.txt

9.)Check the services on the OS and make sure the AV product is not running in anyway and if it is, stop the service.

10.)Restart the Domino Server without rebooting the OS and having the 3rd Party Tools disabled can you connect:

Win2000: Issue a netstat -an > C:\netstat6.txt
Win2003: Issue a netstat -abn > C:\netstat6.txt

11.) After the above has been completed please collect the WINMSD report from this server ,

(2000)Go to Start / Run / WINMSD / Action / Save as system information file, *.nfo
(2003)Go to Start / Run / WINMSD / File / Save as a system information file, *.nfo

12.)You can also download this tool for free from Microsoft to show you the connections on your server, there is no overhead and this will give you a GUI showing which product is using what ports, try it on your client:

http://www.microsoft.com/technet/sysinternals/Utilities/TcpView.mspx

When you collect all the files mentioned above please zip them along with the NSDs , console log and semdebug.txt, sysinfo.log, netstats.txt and send them up to lotus_support@mainz.ibm.com making sure the subject line is the complete PMR# with commas.

13.)
After this has been completed with the Domino server down complete the following

Rebuild the Page file on the Domino Server:

Start-->Settings-->Control Panel-->System-->Advanced->Settings-->Advanced-->Virtual Memory-->Change

Set the Page file to 0 for both values. Set it and reboot the OS. When the server comes back up set it back to the value you had it configured to and again reboot the OS. When the server comes back up a new Page File will be created.

*Now that the Page file has been recreated ensure that the Hardware for the Network Card is up to date and the Anti-Virus is also up to Date.

I hope that you have found this information helpful - I have used it to resolve this issue multiple times.

Please respond with any questions and I will respond as soon as I can - I tend to check the Forums often.

Regards,
-Bob

Feedback response number RJAS83UQWL created by ~Kim Desfooterjip on 03/24/2010