We have been working with TFS 2012 (Windows Server 2008 R2) successfully for a couple of months. Just now, I did a repair of .NET Framework 4.5 on the TFS machine (I was missing some files for a build) and did a reboot of the machine - the first in a long time.
And now:
I cannot access TFS from its remote IP-address as I could before the reboot (http://ipaddress-numbers:8080/tfs). Not from my local machine, and not logged in to the machine itself. Not accessible by Visual Studio, nor browser.
I can access it through http://localhost:8080/tfs logged in to the machine
From what I see, the binding to port 8080 is correct in IIS, and the port is also open for all in Windows Firewall.
After the reboot the network connection had changed from being classed as Private to Public. And so the firewall was set to not let through Public connections to the TFS.
I did the troubleshooting by disabling the firewall and seeing that the connection was let through...
Related
I have 3 RDP's (2 of Windows server 2012 R2 and 1 Windows Server 2008 R2). By using Microsft Remote Desktop, I am able to get connected remotely with the two Windows Server 2012 R2. But I am unable to connect with Windows Server 2008 R2. I am getting the below error.
Previously I was able to connect with all three. Also, I want to mention that in the windows environment I am not facing any issue with the RDP.
I am stuck to it and don't know what to do. Any help would be highly appreciated.
I had this issue and this is what I did to get working back the RDP client on a Macbook pro mid-2015 with the last big sure release.
First make sure that :
the remote server IS online
the remote server IS accepting RDP connections
the remote server firewall IS configured correctly with the right port
the remote server IS NOT configured to accept only connections with NLA
After validating the above points, then on your client (the Mac) you can try to get working the RDP with this first step :
remove (please make a backup) the file UBF8T346G9.com.microsoft.rdc located in /Users/[Your username]/Library/Group Containers/ then reboot your Mac.
If it still doesn't work, you could try to remove the app, reboot, then re-install the app again.
You can also analyze the Event-Viewer on the 2008 R8 server to see if there is something to help you to spot the issue.
More information about troubleshooting RDP :
https://learn.microsoft.com/en-US/troubleshoot/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors
I faced the same problem some years ago.
here's the solution:
Read the article carefully. https://learn.microsoft.com/en-US/troubleshoot/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors.
And check if the remote server IS accepting RDP connections.
And also check if the remote server accepting only connections with NLA.
delete the file UBF8T346G9.com.microsoft.rdc and Reboot.
And if still doesn't work, then totally uninstall / remove the app and install again and check.
Thank You
I am running two virtual machines on my local computer (Windows Server 2012 R2 and Windows 10 running on vmware workstation 12). My Server 2012 R2 has SQL Server 2016 Developers edition on there and I have Windows 10. Both of them have SSMS 17.7 on them. I am trying to connect to the server on my Windows 10 machine via SSMS. I tried authenticating them, but the Windows 10 VM does not show up. Even when I try to map or even UNC path into any of them, nothing shows up (on both ends). Now, I have tried bridged connection and serial port for both of them and that does not seem to work. Does anyone have any ideas on what may be the problem or can give me a link to do this in? I have tried this youtube link: https://www.youtube.com/watch?time_continue=1&v=GUsyEJda-E0 and VMWare's official site:https://www.vmware.com/support/ws5/doc/ws_devices_serial_2vms.html Thanks in advance!
I'm having troubles enabling remote debugging on sharepoint online. I have 2 machines, my local machine (Windows 8.1) and my development server(Windows Server 2008 R2). On my development server I first tried remote debugging using Visual Studio 2012 Update 4, as described here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug.
When this didn't work I tried doing exactly the same thing on my local machine, which has Visual Studio 2013 (Ultimate) update 1 and the latest windows azure sdk (2.3). This worked perfectly. Thinking upgrading to visual studio 2013 would solve my problem I've installed 2013 (Premium) on my dev server, next to 2010 and 2012. After installing and updating everything for 2 hours however, I came to the conclusion that I received the same error as on VS 2012.
Googling came up with a few interesting causes for this bug: sitenames longer than 20 characters or sitenames containing hyphens. This is not the case. Then I verified port settings, the dev server has no active firewall but I wanted to exclude any possibilities. And low and behold, both telnetting from my local machine as my dev server to ports 4016 and 4018 of my azurewebsites.net url worked.
Are there any other solutions for this bug? Since debugging locally is not an option (sharepoint provider hosted app for project online) this is very inconvenient.
Thanks,
UPDATE: Deploying the site as a cloud service works, and so does remote debugging them. However, we would like to stay with azure web sites for now..
I know this is a duplicate of Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023; but none of the solutions there or on twitter were of any use.
Check out Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023
I think this has to do with blocked ports 4016 and 4018
my host machine is a 64bit Windows 7 Enterprise device. I have vmware player installed and have a virtual machine running XP SP3 for some old fashioned vb6 development. Inside this virtual OS, I can access the internet fine. Virtual Machine Network Adapter is set to NAT.
I also have another virtual machine, running Windows Server 2003 R2 SP2. This is also set to NAT. However, I cannot access the web from inside this machine. Troubleshooting attempted include turning off firewalls, setting the vmware network connections on my host machine to auto retrieve IP & DNS and a long search on google. I found this, http://www.techexams.net/forums/off-topic/27651-vmware-nat-not-working-correctly.html but can't seem to follow the instructions as it's obviously a much older vmware version. (2006!) I also tried disabling "Internet Explorer Enhanced Security Configuration"
Any help would be great. Thanks.
Are you able to connect to your VPS via Remote Desktop? If yes, then check the browser settings for Proxy and see how it connects to internet. If you are using FireFox then you need to follow below steps:
Open Firefox.
Click on Tools -> Options.
Go to Advanced -> Network tab.
Go to Connection -> Settings.
Developing an MVC application, i now need to have test other browser versions.
Installed the VM XP on win 7. That is running good. Got IE8 installed and FF 3.6. I know IE9 has a compat mode for 8 and 7, but read some articles that these may not run exactly as their stand alone versions. I got IE8 installed on the VM XP, so now i need to connect to my IIS Win7 localhost.
IS there anyway to do this? and How?
You need to configure your HOST PC's firewall to allow the VM (and perhaps other machines) to connect on port 80.
You can then navigate to http://hostmachinename in the VM.
Although my firewall was off, i was able to connect using the local machine name or ip address, as stated above by SLaks. So, if anyone has there firewall on, you may have to allow the VM to access the ports.
I did set the VMXP >> Tools >> Settings >> Networking to my Nic/ethernet card.
Not sure if this had any effect.
I also had trouble at first not getting the .NET MVC website to run. But then realized our web.config is setup to take only https. I had my website running on 2 ports, one for is for SSL. When i use the https secure port, it connected. So iguess the web app was seeing the VM as another computer tryingto coinnect, that was not local, so it required it to connect by https.