I want to create a VPN Connection Manager on user's PC. The connection Manager must set up 3 VPN protocols on user's PC for Windows XP, Windows Vista, Windows 7 and Windows 8.
PPTP and
L2TP/IPSec and
OpenVPN
The Connection Manager shall receive server list from our servers.
Please help me to soulve the above issue. I google it since last 2 days bit not find any approproate solution to this. So please help me in this.
You can find details on creating a VPN Connection in .NET using:
Set up VPN Connection using C#
Remote Access Server Spec
However using ASP.NET is unlikely as browsers can't instantiate a VPN connection, they are sandboxed away from that functionality. Even services like GoToMyPC have a desktop client to perform the main functionality.
However you could create the RAS file then provide a download link on a website to it.
You can find the file at:
C:\Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk\rasphone.pbk
The person downloading the file can then just import that and have all the set up provided.
Related
I'm going to be making a fun Python project for myself. This is non concurrent. Only me will use this. I would have a desktop version of the app, with the DB on it. And then my phone would have an app that accesses the information on the DB over network and display the data I want.
For most of the SQLite checklist, seems like a perfect fit for a single user super small project. Except the network part is confusing. Some say no, or yes it's doable but not great. What's the consensus here? If I want to access my DB from my phone from anywhere, is SQLite capable? What problems could I run into with this...
You would have to host your DB somewhere accessible from the internet. By doing this, you open it up for attacks should someone get your server address. You can secure this by setting up a VPN from your phone to the PC, this would allows you to run the SQL server as just a local instance only accessed if you're on the VPN. SQL Lite should work just fine under a VPN setup since it won't require the server to have an open connection out to the internet.
As for problems. If you are somewhere where you cannot establish the VPN connection (firewall, port blocked, etc) you will be cut off from your server.
I have succeeded in hosting my applications locally but when i try to view it through a network outside it fails.
Same goes for my SQL Server, I am able to connect locally.
I have tried to open my port but it keeps failing, Is the port the cause of the problem?
Server Manager is also not found in my IIS
PS. I am using windows 8
Please help, it would benefit my school project alot
You need to open port 1433 for access to SQL Server:
Configure the Windows Firewall to Allow SQL Server Access
Similar question here.
You will also need to enable Named Pipes and TCP/IP in the SQL Server Configuration Manager.
I'm trying to automate some system using Siemens PLC; for that we have developed a WinCC Flexible RT application for control and monitoring, and have also declared the PC based HMI panel as the OPC server. Which is working fine.
Now, when i try to create a OPC Client application either in WinCC or Labview, on the same PC, am able to access all the tags of the server on the client, am able to do so.
When i try to create the client application on some other computer connected over the local area network [perfectly fine and well configured network working], am unable to access the OPC server/tags in that case.
What can be done in this case.?
The easiest way to establish connection between OPC client and server applications is to perform the following:
turn off the firewalls on both machines
create the same windows account on both machines using the same login name and password
for windows account (pointed out in 2) allow all "access permissions" and "Launch and Activation Permissions" by running "dcomcnfg" command and navigating to "console root->component services->computers->my computer->com security"
The more detailed example of how to do steps described above is given in this article http://opc-da.com/Winsetup.html
Also, there is a powerful OPC client API implemented on LabVIEW using OPC .NET API with detailed documentation on how to use: http://opc-da.com
It would be helpful if you mentioned the OS on the server and the client computers. Anyway, I'm guessing that this is a DCOM issue, as #Ken mentioned.
It's been a while since I worked with this sort of thing, but you can try this article: http://www.opcactivex.com/Support/Tutorials/DCOM_Tutorial_-_Configuring_th/DCOM_XP/dcom_xp.html and see if it helps.
Make sure the firewall isn't blocking the connection. Disable it on both sides.
Take a look at this NI article: http://zone.ni.com/reference/en-XX/help/371361G-01/lvhowto/psp_firewall/
keep in mind, the tcp ports used by OPC/shared variables changed somewhere between LV2009 and LV2011, so depending on what version you have, the ports may be different.
In addition to the ports and the firewall...
Make sure that the account in which the the OPC client is running has access to the OPC server, either through the DCOM default settings or the OPC Server-specific settings (also part of DCOM configuration) on the server machine.
I am unable to connect, for example, via http to a brand new installation of 64-bit Windows Server 2008. The server is on a domain, but is not DC (that's another problem altogether).
The IIS7 is running on the server and the website is accessible locally via http://localhost, but when I try to connect from another machine on the same network, the connections is refused, even though Windows Firewall is disabled.
I am able to connect to and browse the shared folders on the server using Windows Explorer, so it is not a physical connection issue. I can ping other machines on the network from the server, but trying to ping the server from another machine results in "Destination host unreachable".
As far as I can tell, the server refuses any TCP connections from any machine. I am thinking, there must be some other configuration setting that I am missing... Please, help.
NS
Like in Windows 7 the behaviour is determined by the network type (home, work, internet) the OS thinks it is connected to... even with a disabled firewall it respects these settings and accordingly refuses/allows connections...
The solution is embarrassignly simple, and the credit goes to Ashley Steel, on ServerFault.com for asking just the right questions. It turns out that the DNS was resolving the name of the server incorrectly, because the machine was named the same as an old, since decommissioned workstation that used to live on the same subnet.
The solution: rename the server.
NS[Now hiding under a rock]
I have an application that runs transactions spanning over multiple databases on the same server. Naturally this involves the Microsoft Distributed Transaction Coordinator and everything works like it is supposed to.
Howver, when I remotely connect to the network where the server is hosted via VPN and run the application on my local machine I receive the following error:
System.Transactions.TransactionManagerCommunicationException:
"Communication with the underlying transaction manager has failed."
Caused by:
System.Runtime.InteropServices.COMException:
Error HRESULT E_FAIL has been returned from a call to a COM component.
Here is the stack trace for the originating exception:
at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel, ITransactionShim& transactionShim)
at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
The problem arises only when I connect to the server through a VPN tunnel.
Note also that I have temporarly disabled Windows Firewall on my local machine, just to be sure it doesn't block the MSDTC.
Does anyone know of any issues when running MSDTC through VPN?
I suggest you run DTCPing (available from the Microsoft site somewhere) This is run at the same time on both machines and detects all manner of DTC problems.
Be careful I had great difficulties with this tool until I actually read the instructions and started both sides of the test up before I clicked the start test button.
Do you administer the VPN connection? There might be restricted ports on the VPN. Likewise, do you administer your servers? Your servers might only allow connections from IP addresses on the inside and not on the segment used for VPN service. If you are the administrator, perhaps saying which VPN software you are using will help.
I'm having the same problem using a Windows 7 x64 client and a Server 2003R2 server. I have been able to make it work (on the same vpn, same server) using XP, Vista x86, and Windows 7 x86. I have a support call with Microsoft open and they are looking into it. I'm curious - what operating system are you guys using on your client machines?