"Client SVN not accessible (commit/update) from office Laptop/desktop when connected with home internet. Same client SVN is accessible from personal laptop using internet settings. If we connect the office laptop on office internet and use the office proxy settings, we are also able to access the client SVN. seems some configuration issue with the office laptop/desktop."
Any clue to suggestion is highly appreciable.
Related
Our setup:
Server1: Sharepoint is running
Server2: SQL Server is running
Our Sharepoint 2010 was working perfectly fine and then suddenly the website went down and when I tried accessing Central Admin I found the following issue in the error log:
System.Data.SqlClient.SqlException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
I read on internet that this happens when the server loses trust with the domain so I removed the Sharepoint server from the domain and then added it back. Result: Same. No solution.
I also tried other methods where people have asked for updating the host file but that too did not work.
In order to check if the connection is working or not...i did UDL test where I created a file networkcheck.udl on Sharepoint server machine (Server1) and tried running with Windows authentication and tried to connect with DB server (Server2).
Result: Connection successful.
Can anyone please guide regarding this. I don't know why Sharepoint won't connect even after udl test being successful.
Because I don't know enough about your farm as a whole you may be best looking at this as a issue unrelated to SharePoint.
Are bother the servers in the same domain?
Like Dennis said have any of the passwords Expired/Changed?
Do you have anything other than localhost pointing to 127.0.0.1 in your Hosts file?
Check this thread and think of the problem away from SharePoint
SQL Server 2008 Windows Auth Login Error: The login is from an untrusted domain
Thanks
Truez
One of the possibilities of this error could be that the account from which the Server has been installed has been removed from the domain or the account password has been changed.
TFSPreview cloud service is not an option for us
I have install TFS express 2013 on my company network, we have developers at many place in the world so we want give access to the TFS server, but they never can successfully authenticate in the TFS Website, we can perfectly use it from inside.
In the IIS the tfs application: the authentication is set to Windows Authentication others are disable.
We have check the IIS logs and there is not firewall problem, their reach the server but always return a http 401 response.
My server is Windows 2012 and IIS 8.0, and i can't see where activate the Digest authentication as #Mike suggest
Any idea?
thanks in advance
I'm setting up a demo machine with Office and I want to be able to open an Office file using Sharepoint protocol. It seems like in Office 2010 that only SSL connections are allowed.
For this machine, I don't want to have to set up SSL.
This Microsoft article describes a workaround and how to configure it to use Basic Authentication, but it doesn't apply to Windows 2008. The Mr Fixit app fails because it doesn't work on Windows 2008 and the manual fixit doesn't apply.
This registry key doesn't exist in Windows 2008:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient
How can I enable Basic Authentication for Office 2010 on Windows 2008?
Create the above registry key? The description in the fixit makes it sound like it should already exist on those other Windows operating systems.
Considering that the WebClient key is missing it sounds like the WebDAV client is not installed.
A quick Google search yielded this:
On my Windows server 2008 system web client service is missing. Why so?
In Server 2008 edition, default setup does not have web client service. You need to install Desktop experience package to add web client service.
I have written a program that uses webDAV to download documents from a sharepoint server. It works well with client OS (XP, Vista, 7) but it doesn't on the 2003 server it's supposed to work.
How can I enable WebDAV client (not server) on Windows server 2003 x86 ?
On Server 2003 Web Folders (WebDAV client) is not installed by default. You can install it from Microsoft website: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15123
Note that this will install Web Folders extension. In case you wish to use Map Network Drive wizard (mini-redirector, another WebDAV client) follow this steps:
Make sure WebClient service is running. Open Services snap-in and find WebClient service. On Windows Server 2003 this service is disabled by default. If the service is disabled open WebClient Properties dialog and on General tab set Startup Type to Automatic. Restart the computer.
Your WebDAV server must be located on a default port 80. Map Network Drive wizard will fail to connect to any ports other than 80 displaying “The network path http://server/folder/ could not be found” message. Map Network Drive feature does not support SSL / HTTPS connections.
Your WebDAV server must accept anonymous connections or use Integrated Windows Authentication. Map Network Drive will fail to connect to WebDAV servers using Basic or Digest authentication. Use NTLM or Kerberos instead.
Connect to a folder on a WebDAV server rather than to the site root. The Map Network Drive wizard on Windows XP and Windows Server 2003 will fail to connect to URLs such as http://server/. Instead specify an existing folder: http://server/folder/.
The WebDAV client should be installed on all Windows since Windows 2000. Probably the service is not on by default for server platforms. Check if the WebClient service is running.
I am new to TFS and trying to setup where remote users can access the Source Repository and Work Items without having a VPN to the local network.
Is this possible?
From what I've seen the answer is NO. The TFS Proxy component does NOT appear to be what is needed to allow remote access, but rather a way to improve speed for remote users as long as they have VPN connection.
So how can configure TFS with NO VPN requirement?
Thanks ...
The second problem is how will you authenticate them? If you can't VPN to the network, there will be lot's of issues with the Domain access to the TFS.
Home made solution is to create an machine in DMZ and open it via RDP to the remote users (it's not safe at all)