I hosted some WCF Services on my client machine and this machine is connected to internet through any DSL. So, there is no live IP or any other static IP associated with it. Now, I want to utilize these WCF Services on my webpages through Asp.Net.
I need to ask, is this possible to access WCF services hosted on a machine which is connected through simple internet?
Few other things to keep in mind that, client (WCF services hosted) and server (Asp.Net pages hosted) in totally different domain. But, I know client machine IP or MAC address.
You can use services like www.dyndns.com to setup something like that.
Related
I'm developing a windows form application which I want to host webapp to the LAN when the application first loads. From there I want to also have a database accessible over the same LAN connection so that I can post information and communicate between the 2 vb applications.
My question is how you think I would best host the web application from vb. Obviously I need to identify the network parameters so that I can find a port etc, but how should I go about hosting the webapp?
I only need it to go to the LAN and not to rest of the world.
Thanks
Can we just use remote connections when we need to connect to remote database on remote server?
or we should use web services and what is the web service Architecture? is it differs when we use Lan or internet?
To put it simple: web service are based on remote connections (TCP-connections) between server and client. However web services use standard formats to code and transport requests and answers. There are standard libraries for every platform, taking care of the communications.
The benefit of using web service over remote connections is that you do not have to bother with sockets, coding messages into streams and all the puzzle things. Instead you concentrate on your business logic.
In case of internet, you will need to access a proxy server to access internet. Almost every organisation has proxy server for HTTP and HTTPS, they can be used for web services directly. If you use your own remote connections, you may not able to configure the proxy server to let them through.
This probably sounds like an 'out-there' idea, but I would like to host non-HTTP services inside Azure Websites. I would like my code to be able to respond to FTP or SMTP requests on port 80, in addition to HTTP. Specifically, I would like to take in files from a net camera via FTP, process them, and store them in blob storage, etc. I'm aware I could do a VM, but Websites appeals to me because it is cheaper. Is this even possible?
At this point in time it is not possible to host protocols other than HTTP or Web Sockets in Azure Websites - now known as Azure Web Apps.
You can do it in Cloud Services or in VMs, but not in Web Apps.
You can submit feature ideas or suggestions to http://feedback.azure.com/forums/34192--general-feedback .
Hope this helps. Healy in Tampa.
We have two servers, both are containing a local application connecting to local web service, applications and services are identical on both servers.
One of the servers work just fine,
The other one is just dead, I have impression the the security configuration are different on those servers.
What prevents an application X from connecting a web-service, given that another application y on the same server can connect to it. and X is a windows service.
What I should check, what is chances?
Thanks
Check if there is any firewall that might need to some ports opened up.
Could there be any kind of AntiVirus or similar set up on one of the servers?
Basic troubleshooting of loosely-coupled applications means independent testing/verification of those services.
Can you access the web service locally through a different application, i.e. a web browser? If you can't reach the service through the browser, then the server configurations (at some level) are not identical.
Only after you're certain the service is reachable should you look into issues with the windows service.
I have an ASP.NET 2.0 application that I am deploying to an IIS 6.0 web server. My ASP.NET application is being deployed as a virtual directory. Currently, this ASP.NET application is publicly visible on the internet. However, I need the ASP.NET application to run only inside of my corporate firewall.
How do I configure my application so that individuals outside of my company canNOT access/use the web application?
Thank you,
I would do one of the following:
if your app is standalone
1: create separate site for your application with DNS host name that is internal
if not
2: apply security to your virtual directory (windows auth can be seamless)
I suggest,
Use the corporate firewall to block all external requests to this IIS server. Consult your IT guys, as that's quite easy for them to do that for you.
Or use IP policy in IIS Manager to allow internal IP range but block all others. This is simply a workaround, which has worse performance than 1.
Probably a question best suited for ServerFault but you will need to have an IP address that is only internally viewable from the corporate firewall. You probably have an IT department so ask them for a internal only IP address and then assign the IP address they give you in IIS.