Everything seems to be functioning normally, emails are coming in and being filtered etc, but when using the NST admin interface, when I attempt to look at the "log" or "report" tabs I get a connection refused error. However, it does show me the log and/or report. I checked the "File, Connect" setting and have it set to "localhost:8086".

Same with me. I have running the latest release of NST on my production server without any problems. But on another server with Small Business Server and Exchange, I can't connect the Admin Interface to the service.

> Same with me. I have running the latest release of NST on my
> production server without any problems. But on another server
> with Small Business Server and Exchange, I can't connect the
> Admin Interface to the service.

I seem to being having this trouble as well. I can fix it by removing the changes I made to the configuration that pushed the size of the nospamtoday.cf over 98kb.

I can make whatever configuration changes I want and they work just fine as long the config file stays below. However as soon as the size ok the disk is 99kb or greater and the admin tool no longer seems to be able to read it.

The admin wizard on the windows version may have an issue with nospamtoday.cf files larger than a certain size. On my system this size seems to be 99kb or larger. Once the file reaches that size (either by adding new proxies or new options to existing proxies), then the wizard no longer works. I can't really tell for sure if the service stops working also, but this seems to be the case.

I have submitted a pair of emails to techsupport with the particulars of my system and examples of working and non-working config files.

ron.gooding wrote:
>
> I can not telnet to localhost 8086. How can I tell which port
> NST is using?

You'll find this info in the log.

The SBS has an SMTP service running, did you already disable that? If you did not, the NST service will fail to start.

Perhaps it is worth a try to change to a different port, e.g. 80 (if you have no web server running on this port)
You can change the default admin server and port by adding the following lines to the HTTPPort section of the config file, like this:

IncomingServer="localhost"
IncomingPort="80"

Now you can try telnet to localhost 80.
In the admin console, you can change the connection settings to localhost:80 (File->Connection).