I am working on a C# .Net MVC application that uses Windows authentication. When I am in the office, on my work computer, all is well. However, the same code base on my personal laptop will not authenticate. I'm not sure what username:password combination it is looking for. I have tried both my local credentials and my work credentials. I am connected via VPN to the office and can browse network resources, connect to SQL servers, etc. I suppose to complicate matters, I log into my personal laptop using a Microsoft account (which I am considering dumping).
Is there any other info that you need? What else can I try. I can't figure out where the entry point into my code is happening to attempt a debug.
Related
I have to create a Lync 2010 bot. The initial idea that I pitched for the development purposes was to create the application on my own laptop and add the application as a trusted application endpoint to the production lync server. In that way I can develop and test the bot on my machine.
But, this idea was not highly encouraged by Microsoft themselves and they recommended to create a development lab environment to develop the application. I have done my fair share of research and have come to conclusion of adding 2 VMs -
1) 1st VM will serve as the AD server. My question is, what all things/roles should be added to this server like DHCP, DNS, IIS etc.?
2) 2nd will be Lync Server. Here I will create the connection with the AD server. Again, how will the connection be done? What extra roles should this server fulfill?
3) My laptop will act as the application server and I will add my laptop and the application as an application endpoint to the Lync server. Can I create all the three things on a single VM and not worry about multiple VMs?
4) Do I need an exchange server? If yes then why?
Any help is appreciated. Thanks.
Working out of office using VPN to our domain with a C# web application, ASP.NET and .NET 4.5 (not MVC). My laptop is not in the domain. I have an "impersonate" statement in the web.config which all works perfectly in the office (PC there is in domain). When running on the laptop, and the code comes to connect to the UNC drive over VPN, I get "username or password is incorrect".
I've tried setting the "processModel" entry in the IISExpress applicationhost.config file to the same credentials as the impersonate statement but this makes no difference. I understood from searches that this should make the IISExpress application pool run under those credentials.
It is tricky putting the laptop in the domain for other reasons (internet not always available) and I'm not even sure this is the problem. I've also used "cmdkey" to store the network credentials locally.
Any advice would be much appreciated - I've researched this for many hours and also modified "windowsAuthentication" and "anonymousAuthentication" in the applicationhost.config file from "deny" to "Allow", and set their corresponding "modules" to true from false. Nothing makes any difference, nor does running IISExpress with admin rights. Apologies in advance if this is a stupid question, but I often have to do remote support, and I also test the impact of upgrading 3rd party components before updating the office PC, so I need to solve this if possible.
Is it possible to intercept network calls with in windows 8/10 mobile? If not how does VPN apps work in mobile?
I don't think there is a way to intercept network calls.
There is programmatic support for managing VPN connections though. Windows.Networking.VPN namespace is what you are looking for. As stated on the linked page, access to this namespace is restricted for applications published to the store:
If your app is using this API and you wish to publish your app to the Microsoft Store, special permissions must be provisioned for your Microsoft developer account, or the VPN calls will fail at runtime. This permission is not needed if the application is side-loaded or installed through a different method.
To request permission to release your VPN app through the Microsoft Store, contact msftvpnstore#microsoft.com and include information about your company and your VPN app.
If you have any questions about the VPN API, contact msftvpnapi#microsoft.com.
I suggest you start by contacting one of the above addresses and explain your scenario to get the needed support early on.
I'm trying to create a client-server app where the server runs on the user's machine. I'm looking into either using WCF or Sockets but I have a couple of questions.
I'd like to use WCF but it seems that the user needs admin rights in order to launch the service. Would the user need admin rights if the WCF service was running within a managed application (e.g. a Windows Service)? With sockets it seems that admin rights isn't required to open the relevant port.
How would HTTPS security work in WCF? Since this is a LAN program (user talking from client to their own machine), do I need to purchase a certificate and install it on their machines? I'd rather avoid this if possible as the data being transferred isn't sensitive. Would this be the same if I use SSLStream for sockets?
There are a lot of questions, :), so very short answer on part of them:
You can host WCF even in console application. Windows Services may not require admin properties to be installed on pc.
For HTTPS - you does not have to buy certificate, you can crate your own - there are a lot of examples in the net. But - if your data is not sensitive - you can probably use simple http.
You'll have to pardon me as I wasn't sure where to place this. This overlaps in the areas of C# Web Services and Network/Security management I suppose.
I have a server that runs various web applications. One of them is a web service. The account everything runs under is a local account on the machine. It is not a domain account. I don't know why this was done how it was, but it's one of those things that's just the way is because it's the way it was done.
Super, huh?
Okay so my domain account name is given full permissions on the web serivce. Now, while the account the web service runs under is not a domain account, the machine is on our domain and in our network. So, from my computer, I can fire up a browser and type in the url to the web service in this fashion:
http://serverhere:porthere/servicename
Now the fun part. From a different machine on the same network and logged in my domain account, I cannot load the web service.
Here is the really, really nutty part. From both machines A and B, I cannot ping the server hosting the web service. Might be because pinging is turned off.
So the million dollar question is, does any one have any idea's at all as to why computer B cannot access the web service while computer A (my machine) can?
The server hosting the web service is running windows 2000. My machine is running windows xp. The machine that cannot load the web service is running Windows 2003 SP 2.
Check to make sure the subnet masks for both machines are the same; if one subnet is more restrictive than the other, it'll basically ignore messages from that machine.
There are too many options for this. And I would not bet on account permission issue. You should check the communication with network sniffer, like wireshark or network monitor. Check proxy settings. and post more information about the error you receive.
Silly suggestion, but did you check the firewall settings on the 2003 machine?