Here's a super doozy I can't figure out.
Windows 7 Home
I connect to work using Citrix desktop. I access a secure html site using my domain credentials, which triggers a download and starts Citrix
This worked normally up until this morning. I lost network connectivity when my router started behaving badly. After regaining the internet, I attempted to login, but was told my credentials were invalid and locked out. I tried chrome, Firefox and ie. Same result. I assumed i mistyped and got myself locked out.
Call to the network admin told me my account was fine.
Retried, still no joy. On a hunch, I switched to my wife's old profile on my computer since she used to work on it, and she uses the same Citrix desktop receiver.
Signed in as her, got to the desktop, opened ie, hit the same site, entered my credentials... Success! Authenticated and download initiated. Retried in Firefox and chrome, same story. No issues when logged into my wife's profile.
Logged out, logged back in as me, tried again, invalid credentials/locked out message.
So, I know my account isn't locked out. Admin confirmed, and I can access it through my wife's. It's not a browser issue, because all 3 work on my wife's windows profile.
Network adapter settings, firewall settings, router settings are all global so if it doesn't affect my wife's local profile, it shouldn't affect mine.
Why would my profile be failing the authentication process outrigh?. I'm convinced it's not even sending the credentials through, just failing outright. But I don't know why?
I'm going to attempt DNS flush tonight and if that fails, try an earlier system restore point. But I'll take any suggestions under advisement while i use my wife's local account as a work around.
Thx in advance.
So dumb.
Wife's local URL was slightly different. Her bookmark was simply:
www.[companyname].com/remote
which resolved to a much longer URL starting with:
assist.[companyname].com/Auth/XenApp/....
and i stupidly just typed in:
assist.[companyname].com
which resolved to
assist.[companyname].com/Auth/Xen[Company]/....
and thats all she wrote.
Related
This is quite a weird issue I'm facing, something I've never even heard of.
I have 2 hosting accounts on liquidweb's servers. Both shared. At home, I'm not able to access sites on one account. At work, I'm not able to access the sites on the other account. Both work and home have the same ISP.
When I can't access, the multiple browsers I've tested on just can't connect, with the error "Failed to connect". Everything else works just fine. Pinging also times out.
I'm using a macbook pro if it helps.
Spoke to the support. Apparently my ip's were blacklisted by their firewalls when I failed to login in to the cPanel after a few attempts. And ironically, I'd forgotten them at home, and workplace seperately (thanks to my password app failing).
All sorted. Thanks for the trouble guys.
What would cause an emulator unable to view the network UNC shares? When attempting to open any computer on the network via 'Open Path' or Internet Explorer, I am tossed "The network path was not found." followed by "Network resource cannot be found or you do not have permission to access the network." Things to note:
Connecting to the IP address does not work.
I am able to browse the internet via the emulator.
ActiveSync has been configured appropriately and I have installed the needed drivers for the adapter, and the emulator is cradled.
Firewall disabled/setup with correct forwardings.
Network folder permissions are setup properly.
What strikes me as odd is I have also attempted to browse UNC shares on a physical Windows Mobile 5 device, with the same issue. This leads me to believe something within our network settings is causing this but I'm not sure where to start. People have recommended checking ActiveDirectory security policies, but what policies affect UNC shares? This has turned into a rather serious issue because until I am able to resolve this, I am unable to go through with setting up merge replication. Has anyone experienced this and successfully resolved this issue?
Your network is looking for authentication.
I get that here at my work place, too.
As long as your network key is entered correctly, you should be able to try browsing to that same path 2 or 3 more times, still getting those same obnoxious ("The network path was not found." followed by "Network resource cannot be found or you do not have permission to access the network.") messages.
At one of those times, a login box should appear where you type in a Username, Password, and Domain.
You will also have the ability at this point to save your password so you are not prompted for it every time you attempt to access something across your network.
Now here's the real crapper: After you save your Username/Password combination, there does not appear to be any mechanism within the Windows Mobile device to change that password after it expires on your network. You will never be prompted again to change that password, either. You will only get one of those silly messages above because your password is incorrect.
The only solution to this seems to be to reset the device. I have had a question open with Microsoft for about 3 years now, and it has been passed from one forum to another. I've finally just decided that it must not be able to be done, but Microsoft has never written back to tell me that.
I've been happily using Team Foundation Server with Visual Studio 2010 for the last couple of months at my current place of work when it has suddenly stopped working. I get the following errors:
If I browse to the wiki (Sharepoint) on the TFS server it works fine in Firefox but in Internet Explorer it fails with:
No authority could be contacted for authentication.
I'm not aware of any changes to the server or my machine that would cause the errors and other users of TFS are not affected.
The TFS server is on a different domain to my machine, but usually I get prompted to login and using a domain prefixed username works. At the moment, I don't even get a login prompt anymore.
How do I fix this?
I have recently started to experience a similar issue. We also host TFS on a different domain. Twice in the last week TFS has stopped authenticating users, and I have received messages similar to above. I have no idea what is causing this, but on each occasion SQL Server Agent service was stopped. A reboot of the server and a manual restart of SQL Server agent seems to fix the problem temporarily. I'm not sure if this information is helpful, but I would also really appreciate any help in getting to the bottom of this.
We used a workaround to get past this problem. We configured an entry in the Windows Stored User Names and Passwords tool for the domain of the TFS server. It got around the problem of TFS not prompting for credentials by explicitly supplying them via this tool.
When you change your password for that domain account, you must also change the password here otherwise your account can be locked after failing authentication too many times.
I had the same problem, sorted it by upgrading to tfs2012
In my case, I changed the default port 8080 to port 80 and everything worked fine. but the message could also happen due to wrong saved credentials. you can go to the control panel of the windows and search for credentials manager and then remove your TFS credentials.
I'm remote debugging a console app which has some AD functionality.
When I run it on the remote server it works like a charm. (I mean I log in with RDC and literally double click the console app .exe file.)
While remote debugging however, I'm getting an error in the AD related code - "Could not find the domain or the domain does not exist".
Important to note is my dev machine is not on the same domain as remote server. I'm also remote debugging over VPN.
I also want to mention that otherwise the remote debugging seems to be working ok, breakpoints are being met, symbols loading, values populating.
The full source code is kinda long, so I'll just provide an illustation of what is causing the problem:
System.DirectoryServices.DirectoryEntry dirEntry; // in reality this is setup via an ad helper class
dirEntry.rootOU.Children.Find(strOU, "Something"); // BOOM! here is where it can't find the domain
Its not a code issue, and the domain does genuinely exist and is reachable, when code is natively executed on the server, issue only comes in with remote debugging.
Thanks in advance for suggestions on a fix / cause.
After hours of struggling, I found the problem but no solution.
The solution is to have your environments setup in best case scenario if you want to remote debug in an SOA application, connecting to many systems using domain accounts etc.
Your local dev environment should be running under the same domain and account as the account running the remote services on the server. Furthermore, this account needs to have correct permissions in your SOA systems. I.E: If you're working with AD, this account needs to have required permissions. If you're working with Sharepoint, you might need to use the farm admin account. SQL or Databases are much more forgiving because you can configure connection strings.
If you fail to do any of the above, remote debugging can still work for you but it might not. If it does not, what I've found is there is no work around.
You might think you would be able to use No authentication remote debugging, but that does not work with managed code. So (Jan 28th 2010) no solution exists.
I hope this is addressed in the future, because it can be extremely convenient debug remotely.
I've installed TFS 2008, but I can't seem to access the server. When I try to connect to it in Visual Studio, I can't. If I try by browser on a remote PC, I get a generic page cannot be displayed. On the server, I get a 403. Nothing was touched in IIS and the service is running as a Network Service. Any ideas?
try:
http://localhost:8080/Services/V1.0/ServerStatus.asmx. This will tell you if TFS is up and running. If you are getting anything else you need to look into IIS issues.
I wrote a blog post on diagnosing these types of TFS connections.
http://blogs.msdn.com/granth/archive/2008/06/26/troubleshooting-connections-to-tfs.aspx
The very first thing I do is confirm that it works for a known-good configuration – usually my workstation.
Providing that works and the server appears to be functioning, the next thing I do is ask the user to call the CheckAuthentication web service using Internet Explorer.
The URL for this is: http://TFSSERVER:8080/services/v1.0/ServerStatus.asmx?op=CheckAuthentication
By doing this check, I am doing four things:
Eliminating Team Explorer from the picture
Eliminating the .NET networking stack from the picture
Ensuring that Windows Authentication is working correctly (that’s why I say IE)
Ensuring that proxy settings are set correctly
In most cases I’ve seen, the TFS connection issues are because the proxy settings have changed or are incorrect. Because .NET and Visual Studio use the proxy settings from Internet Explorer, it’s important to have them set correctly.
In rare cases it’s beyond this. That’s when I start looking at things like:
Can you resolve the server name?
Can you connect using the IP address?
Are there HOSTS file entries? (see: c:\windows\system32\drivers\etc\hosts)
Can you ping the server?
Can you telnet to port 8080?
Does the user actually have access? Run TfsSecurity.exe /server:servername /im n:DOMAIN\User to check their group memberships
Have you changed your domain password lately? In some cases they’ll need to logoff the workstation and log back on again to get a new security token.
Is the computer's domain certificate valid? update the certificate: gpupdate /force
Hope this helps.
Turns out the time and date on my computer was not "close enough" to the time and date on the tfs server. Changed my system clock setting and problem went away.
What happens if you send a simple HTTP request to the server directly?
ie:
telnet 8080 [enter]
GET / HTTP/1.1[enter]
[enter]
[enter]
That might give a hint about whether IIS is actually serving anything. If you can do that on the server, what about from a different machine? If the results are different a good guess is there are some security/firewall issues somewhere. HTH a little.
I went through everything on a similar problem.
I logged onto my tfs server and connected directly there.
I also used a TFS admin tool I downloaded some time ago from Microsoft, and made sure I was in all the right groups and projects.
I then went back to the client PC with the problem, tried the services/1.0/serverstatus.asmx?op=CheckAuthentication Url again, and it worked this time.
AFter that full service was restored to my PC.
So I don't have the exact answer, but I would go through the checklists presented by Grant Holliday in his answer.
Add this to the cases for future users, as i had this issue on server 2016...
if your firewall allow only Domain and Private Network, it may not work on client. make sure you give public permission, if server network is set to public...
The error you may face:
ERR_CONNECTION_TIMED_OUT
for
http://fserver:8080/tfs