I have this scenario in my local network:
[picture] http://fekt.datagrid.sk/DATA/stackoverflow/scenario.PNG
Windows 2012:
Only IIS installed and configured, TFS installed and configured.
TFS configuration:
[picture] http://fekt.datagrid.sk/DATA/stackoverflow/config.PNG
When I run Visual Studio 2012 on win2012 machine, everything works perfect.
I can check-in, check-out changes, i can go to web access(http://win2012:8080/tfs)
From Desktop PC (Win8, VS2012) I can not connecto to TFS.
Do you have any ideas?
Thanks.
It is most likely the windows firewall.
I would suggest you add the port in question and application to the windows firewall exception rules.
You can quickly test by turning it off but remember to turn it on again once you have tested.
Is it a DNS or WINS issue?
Try to ping win2012 from your desktop PC.
Maybe you can try use IP to access the TFS by http://xx.xx.xx.xx:8080/tfs
Related
We are facing a issue when rolling out changes to application server, following are the two tasks in the release definition
Windows Machine File Copy - which works fine
PowerShell on Target Machine - Fails, Error : The WinRM client cannot process the request
Following things I've tried but still no luck
Allow traffic : Open firewall on port 5985/5986 for source/destination
WinRM service is running on target server
Configuration
TFS 2015
Source server : Windows Server 2012 R2
Target Server: Windows 2016 Serer
Could you please assist us on this, thanks in advance.
i would like to upgrade my production TFS 2017 to TFS 2018.
according to the requirement, it need SQL Server 2016 SP1, because some reason, i decide use a new production server for it.
Before doing the production upgrade, i do the upgrade test in my testing enviroment, the step is
Install SQL Server 2016 SP1
Restore the TFS 2017 Database
Install TFS 2018 Update 1
Start the TFS Upgrade Wizard using my existing db
Confirm the 8080 port is allow to connect
After finish, i can access the TFS web on the testing environment server by using http://localhost:8080/tfs or http://SERVERNAME:8080/tfs (btw Chrome only can access using localhost)
When i connect http://SERVERNAME:8080/tfs on client pc, it doesn't work, it show me
ERR_CONNECTION_REFUSED
All my server have join domain and i try troubleshoot from tfs application to firewall, no any result on it.
Is there any step wrong or other problem on it?
UPDATE:
After i reinstall Windows OS, it's work.
Try below items to narrow down the issue:
Using IP instead of the SERVERNAME in the URL, then try it
again.
Clean local caches from the client machine (TFS caches, Browser
caches)
Restart the TFS wensite from IIS manager.
Restart IIS with command: iisreset /noforce
Try changing the port number for you TFS
Rebuild the client cache.
After you move, restore, rename, or fail over a data-tier or
application-tier server, you must refresh the cache for tracking work
items and users must refresh the version control cache on client
computers.
UPDATE1:
Just try below things:
Add the client machine name/IP to the hosts file. (The hosts file should be located under c:\windows\system32\drivers\etc\hosts)
Try to detach the collection then reattach it again
Try to reconfigure the TFS.
UPDATE2:
Based on geraldlim's comment below : Turn out that after reinstalling the OS and install IIS and TFS in a clear environment, it's working.
We just upgraded our TFS 2013 to TFS 2015. We use VS2015 to communicate with it(we were already using it with our TFS2013). The server was not available during the time our IT made the upgrade.
After the ugprade, everybody started to work again with the server but I was seing it as Offline and I finally decided to remove the server and add it again.
When I add it again(200% sure of all the settings), I get this error:
I finally tried to do the same on our "old" installation of Visual Studio 2013(same computer, same account), and it works. I was at least capable to commit all my changes to the server.
I tried to go on the portal and click on `Open in Visual Studio", and I got another error(TFS400324):
Now I'm trying to regain access to TFS2015 with my VS2015. I can access the web portal.
Here is what I tried after some research:
Do a Repair of Visual Studio 2015
Check that I've no weird proxy
Check that there is no available update(already at VS2015 UPD 1)
Clear the cache of all my Internet explorer
Cleared %LocalAppData%\Microsoft\Team Foundation\*.*\Cache
Run VS2015 in admin
Disable my antivirus
Delete registry key HKEY_CURRENT_USER\Software\Microsoft\VSCommon\*.*\ClientServices\TokenStorage
Check that I've no proxy declared in: C:\Windows\Microsoft.NET\Framework\v*.*\Config\machine.config
I did a windows update.
I ran the command devenv.exe /resetuserdata
Any clue what is happening and how to solve it?
VS 2013 can connect to TFS 2015, but VS 2015 can't. So the issue is on client side. Try on another client machine to connect TFS 2015 with VS 2015 to check the result.
Clean the client cache: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache and C:\Users\username\AppData\Local\Microsoft\Team Foundation\6.0\Cache. Make sure both 5.0 and 6.0 folder are cleaned.
Clean server cache on AT machine: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data, and C:\TfsData\ApplicationTier_fileCache
Remove all credentials in Control Panel\All Control Panel Items\Credential Manager.
Remove TFS server in Team Explorer: go to Manage Connections--Connect to Team Project--Servers, select TFS 2015, remove it and add it.
Connect TFS 2015 with it's IP address, not server name.
This answer will not please to anybody coming here for an answer, but I had to format my computer and do a whole clean install on it.
A little trick might help.
Change port 8080 to another port. I've changed to port 5000
I hope to be useful.
While loading any new project in Visual Studio 2012 and connecting with Xamarin Build host provider, it gives error "Connection to Xamarin.iOS Build Host failed. Double click here to attempt to reconnect/select a server"
Followed below mentioned steps but none worked.
Tried to unpair and pair again from VS 2012 and MAC Build host provider
HKEY_CURRENT_USER\Software\Xamarin\MonoTouchVS\KnownServers remove this key from Registry but I was not able to find this registry
HKEY_CURRENT_USER\Software\Xamarin\MonoTouchVS\MonoTouchBuildServerAddress remove this registry key but didn't help.
Someone suggested to disable proxy by following below steps.
I had the some problem, all was configured well but got the same error. The solution for me, was to disable the proxy! on the windows machine
Hope that will help you
Could anyone please suggest how to disable proxy and on which PC Windows / MAC? And let me know if that helps you to resolve the issue?
Thanks..
Any other solution to get this issue resolved?
==========================
Updates on 24 July, 2014
Solution to my question above I found is: Network connection and constant PING to my MAC PC was broken and thats what causing the problem to connect to Visual Studio.
This works for my machine but not sure about yours.
Go to Xamarin Studio on your Mac, update Xamarin.
Reboot your Mac (just to be absolutely sure)
Startup the iOS Build Host on Mac.
Go to VS on your PC, when VS is trying to connect to the Build Host, make sure the IP address is correct (i.e. your Mac/build host machine IP).
If the IP Address is incorrect (which is my case), try manual connect by entering your Build Host IP Address and try to connect again.
Good luck.
I'm new to Microsoft TFS and it seems like the default of TFS is connect via a Local Area Network (LAN).
Another team member lives in a different part of the world. How can I allow him to connect to my TFS Server, which is installed on a Vista Machine so we can share the same project?
You can either open up port 8080, or install SSL for TFS. You can find more information how to access TFS remotely at http://msdn.microsoft.com/en-us/library/bb668967.aspx. It is an article for TFS 2005, but it still applies.
Simplest is to set up a VPN, let the user log onto your network and then access the TFS server as you would locally. This is the way I do it; saves the hassle and security headaches of trying to expose TFS over the internet.