MIS Systems Thread, Sims reason 0 for remote hosts only in Technical; I have a situation where sims work stations can't login. This doesn't matter which AD username is logged into windows ...
23rd May 2009, 10:35 PM #1
- Rep Power
Sims reason 0 for remote hosts only
I have a situation where sims work stations can't login. This doesn't matter which AD username is logged into windows and which Sims user is logged in.
However if the user connects to our sims server using RDP and loads sims via the same method i.e. S:\ drive they can login and use sims fine.
I can't find any reason for this so any ideas would be a great help.
I have changed the connection in the connect.ini from a hostname to an IP and connections seems to be working ok. So would suggest a DNS issue.
Any other ideas would be great
Last edited by adrianm83; 23rd May 2009 at 11:27 PM.
25th May 2009, 05:14 AM #2
DNS sounds the likely culprit.
Do you use a centrally accessed connect.ini e.g. on the S drive? If so, you could try some troubleshooting, by using a local one. So rather than pointing the connect.ini from the local PC to one stored on the server, try putting all the connection details directly on the local machine see if you get the same problems. I imagine you will if you use the DNS name, but not if using IP. But it might rule out an issue with the mapping to the S drive not working...
EDIT: Oh yeah, and sometimes in the past we've found the local sims.ini file has an error in it. usually it's pointing to our old server and wasn't properly cleared from the machine. it's unlikely but worth checking too.
Last edited by vikpaw; 25th May 2009 at 05:16 AM.
25th May 2009, 11:43 AM #3
When you RDP to the machine did you use the IP address?
25th May 2009, 08:34 PM #4
We have had a number of "Reason 0" reported but I think for SQL Express and have been in discussions with Microsoft. We are programming around the issue, but as we can't recreate the problem we need more info.
Please log a case.
4th June 2009, 09:42 AM #5
- Rep Power
I had this problem before, as it's been said before, it was a problem with the dns. I fixed putting a line in the clients hosts file (c:\windows\system32\drivers\etc) with the ip of the sql server and the ip address associated. but there must be an easy and faster way of fixing it by cghanging something in the dns server...
4th June 2009, 09:43 AM #6
Wouldn't it be better to fix your DNS zone properly instead of bodging the host files? That's the point of it, after all.
Originally Posted by joseph
By tech_guy in forum MIS Systems
Last Post: 17th July 2014, 01:25 PM
By GreenICT in forum MIS Systems
Last Post: 15th November 2008, 09:55 PM
By mortstar in forum MIS Systems
Last Post: 5th June 2008, 12:48 PM
By michael_mc in forum MIS Systems
Last Post: 21st November 2007, 10:30 AM
By cophighschool in forum MIS Systems
Last Post: 4th October 2007, 01:22 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)