Domino 5.0.9a on IIS - Server Not Responding
Mike Pedone
stupid/simple question here (in fact, I almost hope I am). Sorry for
the long post, but I don't know what you gurus need/don't need to help
me with this one.
Here's my setup: I've got Domino 5.0.9a installed on a Windows 2000
box that's also running IIS and MS Proxy 2.0. Domino is running as an
NT service. I started this project a few weeks ago when I installed
Domino 5.0.6 on the server and configured it to run in conjunction
with IIS (I used the article from Lotus's support site with the
special tweaks for running Domino on Win2K). Everything was great --
I was easily able to access both my existing html content and .NSF
files (so I know I got the Domino ISAPI application mapping and filter
installed correctly). The Domino server was actually doing very
little -- the HTTP server wasn't running (because IIS was doing that),
all the mail features were disabled, calendaring and scheduling were
disabled, etc. That's OK, because we're only thinking about using the
Domino server for a handful of shared "groupware"-type apps.
I started having some problems with security. Specifically, I had
trouble with users logging in when they accessed .NSF databases.
They'd get a login box (it looked like an NT login dialog), but they
never seemed to be able to authenticate to the Domino server.
However, they had no trouble accessing databases anonymously (assuming
I changed the ACL to allow anonymous access).
In researching the problem (mostly on Notes.net), I found several
posts that led me to believe that part of my problem might have been
the fact that I was running on 5.0.6. I downloaded the MR/MU
incremental installers from Notes.net to upgrade from 5.0.6 to 5.0.9a.
I then ran them, and upgraded the server and our two client
workstations (only two of us are testing it right now). Now:
-- I can no longer access the server from the Notes client (designer,
admin, whatever). When I try, I get a "Server not Responding" error.
It doesn't matter if I'm running the client from a workstation, or on
the server itself -- I still get the error.
-- I have no problem accessing notes databases through a browser. In
fact, I now get a "server login" screen that seems to have solved my
authentication problem.
To troubleshoot, I tried NotesConnect and verified that all my TCPIP
settings were correct. I can ping the server (using its netbios name,
ip addr, or FQDN), but when I ping port 1352 through NotesConnect, I
get a "connect failed" message. Everything else on the server works
fine -- http works fine on port 80, and proxying is working fine on
port 8080.
I also tried tracing the connection from my client (File - Preferences
- User Preferences menu option, "Ports" tab). Here's what the trace
revealed (presented anonymously, for obvious reasons)...
Determining path to server servername/MyCompany
Enabled Ports: TCPIP LAN0
Checking normal priority connection documents only...
Allowing wild card connection documents...
Checking for servername/MyCompany at last known address 'servername'
on TCPIP...
Using address '##.##.##.100' for servername/MyCompany on TCPIP
Using address 'servername' for servername/MyCompany on TCPIP
Unable to connect to servername/MyCompany on TCPIP (Server not
responding)
No answer at last known address
Enabling name service requests and probes...
Checking for servername/MyCompany on LAN0 using address 'servername'
Unable to connect to servername/MyCompany on LAN0 (Remote system not
responding)
Checking low and normal priority connection documents...
Local network connection document found for servername
Verifying address '##.##.##.100' for servername/MyCompany on TCPIP
Using address '##.##.##.100' for servername/MyCompany on TCPIP
Using address '##.##.##.100' for servername/MyCompany on TCPIP
Unable to connect to servername/MyCompany on TCPIP (Server not
responding)
No default passthru server defined
Server servername/MyCompany is not responding
...that didn't seem to shed any additional light on things.
All relevant NT services are starting fine, and there are no unusual
messages in the NT event log. I looked at the notes.ini file, and
everything looks OK to me, but I'm no expert...
So, does anybody know why my server is "not responding"?
Thanks in advance,
Mike
Brett Flagg
1. Make sure your proxy is set to allow port 1352.
2. Create a conneciton document using IP not NotesName...ie
128.200.x.x).
The number one thing I I can think of is your Proxy is also sitting
on the same box as IIS and Domino. You shouldn't do that if that's so.
But if you are, open the port.....
Brett
On 25 Feb 2002 10:16:13 -0800, mpe...@futurecarehealth.com (Mike
Brett Flagg
On Mon, 25 Feb 2002 18:57:51 GMT, Brett Flagg <fla...@yahoo.com>
wrote:
Mike Pedone
Thanks for the ideas. However, I determined the source of the
problem... This is so embarassing that I hesitate to post it here,
but I suppose there's a remote chance someone else will do the same
stupid thing I did.
The Win2000 server that's running Domino has terminal services
installed (for remote admin). I usually access it through the
terminal services client from my desktop (because I'm too lazy to get
up and walk into the server room to use the console). Yesterday, when
I ran the incremental updates to update from 5.0.6 to 5.0.9a, I was
logged on to the server through the terminal services client on my
desktop.
This afternoon, at the peak of my frustration, I decided that I'd
reinstall Domino and start over again. I walked in to the server
room, sat down at the console, and logged on the the server. I was
promptly greeted by a DOS window asking me if I wanted to convert the
notes databases as part of the upgrade (or something like that). This
window, I might point out, never popped up in any of my terminal
services sessions. I pressed the "Y" key, and I watched it convert
the databases and start the Domino server. It seems that it's a good
idea to run the MR/MU updates at the console, not through a terminal
services session.
Everything now works just fine...
--Mike
Brett Flagg <fla...@yahoo.com> wrote in message news:<6a2l7ucjfrung996m...@4ax.com>...
fred
console window in a remote session. :)
Tony Evans
>That's one of the problems with Terminal Server and Domino. Can't see that
>console window in a remote session. :)
Another annoying element is that if you start any product which uses the
domino dll's while in a terminal services session, it kills Domino (at
least on our setup).
--
Tony Evans (ICQ : 170850)
Recommended Author : Stan Nicholls [http://www.stannicholls.net]
PATH=harddrive;drawer;desktop;pocket;boxincloset;boxunderdesk
Gemmell Mania : http://www.gemmell-mania.org.uk
hartmut...@brucks-systemtechnik.de
http://www.uk.research.att.com/vnc/index.html
regards hartmut
Chad Amberg
news:Pine.WNT.4.44.02043...@BK5176.de.marconicomms.com...
> Don't believe that's a good choice for a Win2000 server computer. Think
> it's better to use the integrated terminal server.
>
>
Not for when you're using Domino. You can't see the console when you run
Terminal Server. For that you do need VNC.
--
-Chad
Domino Stuff at http://www.pirate-king.com