Misc notes from Lotus Gold Forum Regarding Server Not Responding Issues
From Support
Potential Items to Check
1.) Log in to Domino Console (WRKDOMSVR SVRNAME) and run the following command to see which IP the TCPIP port is bound to:
SH PO TCPIP
The Domino console will display the bindings. If all IP's are bound to the Domino Server, the port entry should look like this: *:1352, otherwise like this if bound to a specific IP address: 1.1.1.1:1352
2.) Bind the TCPIP port to a specific IP address by adding or modifying the following entries in the NOTES.INI configuration file
TCPIP=TCP, 0, 15, 0 TCPIP_TCPIPAddress=0,1.2.3.4:1352
This example binds to IP address 1.2.3.4.
3.) In the Domino Administrator/Current Server Document, select the Ports/Notes Network Ports tab and change the Net Address to match the bound IP address of the server instead of using a host name.
Using the example above (2.), the Net Address would be changed to: 1.2.3.4.
News Article Details
TCPIP_TcpAddress=0,172.20.16.2:1352
$$HasLANPort=1 Ports=TCPIP
If you want to enable Notes clients to listen on an additional IP interface on a partitioned server:
1. Create and enable a new Domino port that uses the TCP/IP protocol. You can create another one. Say TCPIP2 by changing the NOTES.INI as follows:
Add the statement TCPIP2=TCP, 1, 15,0 Change the Ports= statement to read Ports=TCPIP,TCPIP2 Add the statement TCPIP2_TcpIPAddress=0,x.x.x.x where x.x.x.x is the second IP address 1. Update the Network Configuration document of the Domino server to indicate the new port name and to enable it. 2. Add a connection document on the client that points to the new TCP/IP address. 3. Connect to the server from the client.
The connection record on the client is key. You might be able to avoid it by making sure that ALL Notes clients will access a DNS which resolves the Notes server name to the correct address AND THIS NAME MATCHES THE NET ADDRESS in the server document. Clients use the NET ADDRESS in the server document to determine how to connect to a server. If you use name there and the name resolves correctly, You're OK.
Hey
Most likely explanation is that your Domino server is only listening on one IP address (the ethernet card) and not on the Token Ring card. Go to the Domino console and type "SH PO TCPIP" (assuming your Domino port is called TCPIP) -look for port 1352 in the local address paer - you will see either...
<Ethernet card IP address>:1352 (eg, 1.2.3.4:1352) OR
- 1352
If you seem the former, the Domino server is only listening on the IP address of your ethernet card and that is your problem - you will have a line in your notes.ini something like TCPIP_TcpIpAddress=0,<ethernet card IP address>:1352. If you see the latter then it's ok and your server should be listening on all IP addresses on your 400.
If this is the problem there are two ways round it....
Remove the line "TCPIP_TcpIpAddress=0,<ethernet card IP address>:1352" from your notes.ini - if you do this then Domino will listen on all your IP interfaces on your AS400 (NB - this is no good if you have more than one server on your 400 as you'll need this line to avoid port conflicts.
Add a second port - add a line "TCPIP2_TcpIpAddress=0,<token ring card IP address>:1352" to your notes.ini and enable the port in your server document.
Either way, I'd hunt down a utility called "Notes Connect" - it lets you ping IP addresses on certain ports so you can ping your token ring card IP address on 1352 and see if Domino responds, not just the interface.
Hope this helps
Kurt Alden Domino On AS/400 Infrastructure Consultant kurt_alden@excite.com
We are running multiple domino servers on our AS/400. We got help on this same forum (from James Cioffi) and James' solution worked perfectly. Here is his recommendation:
<snip>
2) Bind each Domino HTTP task to a specific IP address. (This is probably what you want to do.)
Edit the Server document for each server instance. Go to the HTTP Server section and enter the hostname for each specific server instance. You must use a name, not a hardcoded address and the name MUST be listed as an entry on the AS/400's host table (or in the DNS, but I have not tried that. It would be a simple test. If the DNS entry alone doesn't work, then add a host table entry.). Next, change the "Bind to Host Name" field to "Enabled". Then Stop and restart ALL the servers. Make sure to restart the WHOLE server, and not just the HTTP task. This is required for this particular configuration change.
(Note it is possible to affect this change without restarting the whole server, but it's kind of complicated.)
If you want to enable Notes clients to listen on an additional IP interface on a partitioned server:
1. Create and enable a new Domino port that uses the TCP/IP protocol. You can create another one. Say TCPIP2 by changing the NOTES.INI as follows: Add the statement TCPIP2=TCP, 1, 15,0 Change the Ports= statement to read Ports=TCPIP,TCPIP2 Add the statement TCPIP2_TcpIPAddress=0,x.x.x.x where x.x.x.x is the second IP address 1. Update the Network Configuration document of the Domino server to indicate the new port name and to enable it. 2. Add a connection document on the client that points to the new TCP/IP address. 3. Connect to the server from the client.
The connection record on the client is key. You might be able to avoid it by making sure that ALL Notes clients will access a DNS which resolves the Notes server name to the correct address AND THIS NAME MATCHES THE NET ADDRESS in the server document. Clients use the NET ADDRESS in the server document to determine how to connect to a server. If you use name there and the name resolves correctly, You're OK.
<end of copy>
Again, it worked for us. Thanks to James Cioffi!
RE: Solution: Assigning Domino to a specific IP Address,,,,, Posted by Nicholas Dow on 22.Jun.00 at 03:19 AM using a Web browser Category: Domino Server -- NetworkingRelease: All releasesPlatform: I just got it to work with a single NIC, we have 3 IP addresses on it. I used your notes.ini entry, noting that the text before the underscore (_) must match the first parameter of the preceding line: TCPIP=TCP, 0, 15, 0 TCP_TCPIPAddress=0,203.3.69.55:1352
Also, I set up the TCP port configuration when configuring the server to use 203.3.69.55 on the port, you can also set this in the server document: Port Protocol Notes Network Net Address Enabled TCPIP TCPIP Network 203.3.69.55 ENABLED
I'm not sure if this last step is crucial, but it's the one you didn't mention.
Note that the above is all about the notes rpc on port 1352.
To bind HTTP on port 80 to an IP, use the server document, Internet protocols, HTTP: Host name(s): 203.3.69.55 (or use the DNS name) Bind to host name: Enabled
