Hello ironcurtain,
Let's take a look at this one section at a time:
"..when I browse from within IIS manager there is no log in window appearing and I have immediate access to OnTime web.
On the server where the web service is installed, when I enter in IE6.0 browser URL http://localhost/{sitename}/Default.aspx then I have immediate access.
When browsing URL http://{IP}/{sitename}/Default.aspx from my local machine I have immediate access."
This is the behavior you should expect when you've properly configured OnTime to use Windows Authentication. You log into your doamin when you turn on your workstation, and then browsing to the OnTime web URL, OnTime will simply grad that login info and use it to log you right in.
"However my work colleagues are shown the logon window and when they
enter in the {domain}\username information into the login screen they
are given the validation message "Unable to log on to OnTime web -
Login information is invalid. Try again!""
This login screen you mention- is it the OnTime login page, or does a Windows domain login window appear? If it's the OnTime login page, then we should expect OnTime to give you the "Login information is invalid." error because that login page is for entering the regular OnTime login username and password, not for entering in the Windows Authentication info. As in the scenario you described for your own experience, OnTime should have just grabbed their Windows login info and used it to log them in automatically. If they're still prompted with the OnTime Web login page, then that leads me to believe one of the following might be true:
1) The user isn't configured within OnTime for Windows Authentication. Go to "Tools>Manage Users", edit the user, and make sure you've entered in the appropriate domain and username for each user.
2) There is some configuration within your network that is restricting this Windows login information from being passed from the local user's workstation to your web server. As you mentioned, this sounds like some kind of network access might be the most probable reason they're not immediately logged in when they browse to the OnTime Web URL. I would test by giving one of your users access rights to the server and trying again.
Also, Remote Server is definitely not required for the OnTime Web. The Remote Server is used solely with the OnTime Windows client as an alternative way to access the SQL database, and I can't imagine a situation where it should be used in conjunction with the OnTime Web client.
So check your OnTime users' settings, and make sure their workstations are configured to be able to pass that Windows Authentication information to the server.
Let me know if you have any further questions.
Thank you,
Tom Harder
Axosoft Support
support@axosoft.com1.800.653.0024 option 3--'Fear the Bug' Podcast--