Issue accessing the TFS server though the web - tfs

I have TFS 2010 set up on TESTServer.
If I am on the server (logged in as administrator) I can access the web portal for TFS using the following
http://TESTServer:8080/tfs/web/
but when I am on my own computer still in the same network, when I try the same URL, I get challenged for a username and password. Even when I enter the administrator details, it does not accept them.
Also I tried the following
http://TESTServer:8080/services/v1.0/ServerStatus.asmx?op=CheckAuthentication
Which says the resource can not be found
* update***
I got it to work with the IP address... but if I ping the name it gets the correct IP address??
Any ideas?
Thanks

Since you cannot connect to http://TFSSERVER:8080/services/v1.0/ServerStatus.asmx?op=CheckAuthentication it could be that you have incorrect proxy settings in your organization. Could it be the proxy settings have changed?
Have you checked your host file for any entries regarding your TFS server?
Can you open a telnet session to port 8080 on your TFS Server?
Grant Holliday wrote a couple of steps you can do to troubleshoot TFS connection issues.

Related

Jenkins not accessible with http://<hostname>:8080 in Windows server 2012

I have installed Jenkins in Windows server 2012 64-bit machine and want to make it available in internal network.
I have added --httpListenAddress to 0.0.0.0 and restarted Jenkins and tried to access it with http://hostname:8080 but no page shows up(though It showing Jenkins icon in URL bar). However http://localhost:8080 works fine.
Further I checked the firewall inbound rule for the Jenkins but seems it has no issues.
I tried to catch the listening ports with "netstat -aon | find /i "8080" and found <host ip address>:8080 FIN_WAIT_2 which sign towards that the request is stuck(May be I am wrong).
I am clueless what exactly is blocking to use hostname with jenkins. Please share your solution if you already fixed this issue.
You might try adding a Windows Firewall rule. Go to Windows Firewall, Advanced Configuration, Inbound Rules rule and create an Allow rule for the specific version of java.exe you have installed.
This worked for us with the drawback that every time you upgrade Java, you must also modify the firewall rule. This is because Java creates a new subfolder for every version. We've tried using %JAVA_HOME% in firewall rules but it doesn't seem to work. We were on Windows Server 2012R2 at the time.
Similar answer here: https://stackoverflow.com/a/17479566/7752
On the server open a new command prompt and type
ipconfig
You should get a list of ips. Open a browser and type each up followed by 8080 for e.g.
http://202.123.2.1:8080
If Jenkins opens up, from another computer ping the ip and see if you can get a ping reply
ping 202.123.2.1
If you get a ping reply, you can access jenkins from any pc on the network by typing in the ip and port number.
Now to get to the hostname,you need to edit your host file
c:\Windows\System32\Drivers\etc\hosts
Type in the ip followed by the hostname
202.123.2.1 jenkins
If you can't get through, you need to open port 8080. See https://www.vultr.com/docs/how-to-open-a-port-in-windows-firewall-on-windows-server-2012
You cannot access from outside the machine because Jenkins Service does not have credentials to use that machine, only from localhost is accessible.
This is how to enter the credentials in Jenkins service.
In the Windows search bar, type services then enter.
Then scroll down to Jenkins and double-click on it.
In Jenkins Properties, select the tab "Log On".
Select Check box "This account"
Update your username and password.
Voila! Now Jenkins web can connect to the Jenkins machine via Jenkins service.

Jenkins Server - Issues with setting URL

I am trying to set up an internal Jenkins server for our QA team and facing some issues with the server URL. This is inside a corporate network and all sort of firewall and proxy settings are in place, however we need to access the server only with in our internal network. This server runs from a Mac Mini. I was able to install and access the server without any issues using localhost:8080.
I tried to set a custom URL (something like testjenkins.local:8080)under the Manage Jenkins option and never was able to access the server. The only option worked for me is with the IP address (IP:8080). I was able to access the server from other machines in the network using this URL.
The real problem with the above setup is that the machine IP changes(I am not able to make it static), and hence wont be able to get an always working URL.
Highly appreciate if any one guide me in the wright direction.
Given you have a dynamic IP on your server, a good alternative would be using ngrok. Ngrok can expose the port 8080 of that server to the internet via secure tunnels, and you can access it via an URL, so changes in the IP won't affect it.
However, ngrok exposes the server to the whole Internet. To make it accessible only for your team you can add authentication in both ngrok tunnel and Jenkins server (would it work for you?).

TFS Team Web Access - Users being asked for credentials (and rejected)

BEFORE: I had a TFS 2010 on a temporary test environment set up with a project and I had web users and everything worked great.
NOW: I've installed it on a permanent environment (same O/S, domain, everything) but any permissions I set no longer seem to have any effect.
It seems only the service account can access any features.
Authentication is NTLM.
Any network users I give access to are either being asked for their credentials to connect to the server and being rejected regardless (they can connect to the default IIS fine) or they get:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
Ridiculous, but the problem is that the new install was on the E: not the C: so the local NETWORK SERVICE account (that I use as a service account for TFS) did not have access to the files/folders under \Program Files\Microsoft Team Foundation Server 2010\

How do I allow a remote user to access my local TFS server?

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.

Can you please give me a Step by Step instructions to set up TFS in such a way that my team can access it from anywhere in the world?

Basically, Me and my team are working in the geographically dispersed location,My teammate is is in USA and I'm in India. I've Installed the TFS on my development machine (Windows Vista) and I want to my team to access the same exact project which i'm working on anytime,anywhere.
We dont have any funds to buy a hosting account or We dont have funds to create a VPN Account from the internet (my ISP doesnt provide me one...awwww).
I don't run TFS, but this is more of an IT question than a TFS-specific one, I think.
My coworker showed me a trick that precludes the need for VPN, but is still secure. You'll need to set up your firewall to route traffic from one of your WAN IPs to an internal server that allows SSH access. These steps will be router and internal network-dependent.
Then download and install PuTTY or PortaPuTTY. Set up a profile that points to your public WAN IP and SSH port, and also add SSH tunneling to route a port on your local computer to the TFS server IP and port.
Let's say you choose a local port of 12345 and your internal TFS server IP is 192.168.0.100 and the TFS port is 1234. When you connect to TFS with PuTTY, instead of specifying its IP, you'll connect via localhost:12345.

Resources