david_begg

It looks like we have a similar problem here. We have 4 servers operating as domain, print, file and application. Recently 1 of the servers (application) gave us the messsage "Server not accessible. The server is not configured for transactions." The situation is, however, even more bizarre than this: - We get this message when trying to access this server directly through My network places from any computer on the domain. - The applications that are already accessing data from this server are not impaired in any way. There appears to be a path already established to the data that is not effected - Where we have a mapped drive or shortcut to a folder on the server this is not effected either. Hence most computers can get access to the server in some way or other. Consequently we only noticed the problem when trying to reestablish an application link when broken. I had it suggested that we use the following: - Use netshare command to check that IPC$ was in share list. It was not - Added using "net share ipc$". Share appeared. This may be a coincidence but it appears that I gained access very briefly to the drive using this process. This allowed me to establish a mapping on one computer. The share disappeared again almost immediately. Has anyone any other suggestions as to what might be going on here? Thanks David Begg