i've got a strange problem with using WNetAddConnection2.
First of all i connect to a WebDAV folder with correct server name, user name and password.
Connection get established as expected and i can see the mounted drive with the windows explorer.
After that i call WNetCancelConnection2 to remove the mounted drive. Works fine and it disappears from the explorer.
Now there comes the strange behaviour. If i try to connect again to the server it does not matter what password i use, i can take a totally wrong one and the drive get mounted again without any problems. Seems that Windows caches the connection.
I found out that it takes exactly one minute and after that time trying to connect will bring up the expected error message.
My question is if this 60 seconds timeframe is adjustable or what other thing i can do to avoid this behaviour.
Thanks in advance for your help.
Related
This issue tortures me days and still can't fix it: I have a file share server and I can access it from my windows client.
From the client, I am using net use command to connect the file share by using some specific user like:
net use y: \ia0.myserver.com\fs Password123! /user:corpuser2258#myserver.com
I have a script, which uses net use to connect to share by an user, do some file operations, then disconnect from share.
The script will loop on different users to do the above things. The problem is, script is doing well, until about 200 hundreds of loops, then net use will fail. The system error 53 has occurred.
At this point, my client cannot connect to the share anymore. I searched a lot on webs and tried various methods mentioned, like reboot netbios or other related services, but none of them can work.
The only way for now is reboot client, and then everything is back to normal.
Since the scrip works fine every time for the first hundreds of users, there should be no network or server issue. As long as I reboot client the system error 53 issue will gone. It looks like something in client should be rebooted or change to some initial state but I can't fingure out.
I hope someone could help to identify and fix the problem, thanks.
Can you give any other info like network capture (wireshark)
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.
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 am facing a problem that I discovered while I was implementing a small client/host application.
The client side runs Windows 7 64-bit and machine never turns off but user is automatically logged off after 30 minutes of inactivity. When user is automatically logged off the host becomes unreachable, first I thought the problem was isolated to my application, but after som investigation I discovered that resources and vnc server is also unavailable.
The question might be a bit off limit for this forum but I can't find any reasonable explanation somewhere else. Does anyone know how I can keep user being logged off automatically but with the host still reachable on the network?
You need to have them as services.
Are you connecting to some port opened by a server/service which runs as the user? If so, that's the reason. To circumvent, you need to have the service installed/started independently of the user, for entire machine (using administrator priviledges)
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