I have several windows shares hosted on a PC running Win7x64. This machine is also hosting a basic website via IIS7. Whenever I deploy a new copy of the website to IIS any WinXP users connected to the shares on that machine get disconected.
After some period of time (20mins or so) the shares all start working again.
This only seems to affect WinXP clients, with them recieving this error message described here: http://support.microsoft.com/kb/890413.
The resolution provided by Microsoft works, but it means that everything I deploy a new copy of the website all of my users have to go through this hassle.
Any IIS experts out there know what is happening, or how to resolve this?
Thanks
Related
For the last year we've been working from home, and using VPN to connect to the office network for program updates.
Lately we've decided to try to find away to remove the need for that connection, and I would like to remove the need for any kind of file share, as replacing the VPN with a different VPN seems silly.
I know that VS can make a deployment web page and upload it to FTP, which solves half the problem, but I also don't want just anyone who finds the webpage being able to download and install the app.
We have a web server running IIS, and we also have a sharepoint site on office.com
If I install it to IIS, is there a way to secure it to our employees with azure active directory?
Is there a way to put it on the sharepoint site, which is already secured?
I just haven't found good resources to solve either problem.
For the question of is there a way to secure it to our employees with azure active directory.
If you want to do it in IIS level, I don't think it can be implemented. But we can do it in application level. You can refer to this document about how to develop your application with Azure AD.
I have a problem that i have a difficult time explaining, which makes any online search very hard. Here is my dilema.
I'm migrating a VM. The purpose of this machine is to compile send out daily/weekly/monthly reports. I know there are other ways (like Power BI) but this is the situation we are in right now. The older machine has win10 pro and office 365 installed while the new has win10 enterprise version and office 2016 installed. This machine runs 24/7 in the background running specific tasks (via system scheduler app) at given times, that is it's a Virtual machine and has done so without issues since it was created. The reason for the migration is because we need to domain change and bring the machine under a new corporate policy and we don't want to do this on a live server.
We've set it the VM's the same way, same programs and same settings. Everything seams to be running smooth expect for this one thing, and here is the problem i have a hard time to explain or figure out:
MS Access will update the tables and the computer will run the tasks as set but it will not export the data to pdf unless i have a remote desktop connection open. Will not export the pdf's otherwise. MS Access uses a autoexec macro where the pdf export is set with ExportWithFormatting. This works without issues on the old server.
We thought this to be a permission or user specific issue at first but even re-creating the tasks did not work and changing paths. Otherwise also i expect we would have problems with tables updating, specially since it works when you have an active remote desktop conn running.
I'm lost and therefore hoping this community will be able to help or guide me to a solution.
I believe that we found the reason for this. It was caused by windows easy print and the printer drivers of the machine. It worked for some reason differently between the servers. after reinstalling the printer drivers and a few restarts it started working. It exports now from access again.
This is at least solved.
Working in the local environment I'm quite often getting errors on communication between the visual studio, IIS, IIS-Express and the browser (any combination). Everything is working on closing down the computer and doesn't any more when the computer restarts. Problems have started when the computer joined the domain.
I've spend hours searching for a solution to the problem. It looks as Widows Defender is to blame which is triggering different rules after I've joining the domain. It is enough to switch off the firewall, start any web application and enable the firewall. Simple (yet annoying) but working (what is most important).
After working with Windows Server since NT 3.51, this was kind of a first for me. Here's the scenario.
After no issues accessing a Windows Server 2012 R2 network share for 2 years, a Win 7 Pro workstation all of a sudden can access the mapped drive to the share, but cannot see all subfolders underneath it. Only one is visible, not the other 20 or so.
When I log out as the user and login as the domain admin account, the issue persists on the workstation. Just this one workstation.
Nothing has changed in terms of the share or NTFS permissions on the server-side of things.
I look in the server event logs as well as the workstation's and don't see anything striking.
I removed the workstation from the domain and add it again. The issue still persists.
The workaround is that I created a second share to the same resource on the server-side of things. Mapping a different drive letter to this new share, the workstation can see everything again.
My only guess would be some sort of old school SAM database corruption or something? I recall years ago I had a Windows 2000 Server that would lose Computer Browser functionality due to some odd SAM database corruption. The only solution back then was to reboot the server. It was the PDC and couldn't even browse its own network shares.
I um using Windows Azure toolkit for Windows Phone from codeplex. After creating a Windows Phone Cloud Application from a template, I started it on localhost and it run succesfully. Then i followed instructions on Codeplex on how to deploy on Azure, and published it also succesfully - I got an url to the website, but after typing the url in browser the website didn't load, and after a while there was a timeout. I tried both production and staging deployment. Can't resolve why this happens - did anyone faced familiar problem?
The publish completed successfully however this application is not running properly on Windows Azure.
As you are using Web Role type WP7 Phone application look for all the steps suggested in the link below:
Webrole is not starting and always busy
Also if you still could not find the root cause open a Windows Azure support ticket and you will get some help to find the root cause.
You may want to look at:
http://msdn.microsoft.com/en-us/library/windowsazure/hh134844.aspx
Remoting into the VM is a great way to see what is going on. Does it come up if you want for a while (maybe 30 minutes)?