Web services dilemma - vb.net

Hey all I have created a web service that starts on my local intranet and sends out data to an outside server. This works awesome and all using classic asp on the server side and vb.net program sending the info from the intranet pc.
But now I need to do the opposite. I need to have the web service be called from the server web page to the intranet pc. Problem being is that we do not have access to any ports or any means of getting data from the server because of the firewall.
How can this be possible to do with my current scenario above?

Related

Executing a ping from a remote server

Using VS 2015 and VB.net.
I have a web application and I want to execute a ping from a remote server. The server is running windows Server R2 2012.
The server has a router connected to it that goes to sleep periodically and at the moment we log in to the server and start a ping to the router to wake it up. The web application will be accessed by various users and on a button click the ping would start. The web application is hosted on our web server (not the remote server) and the ping must come from the remote server as the IP address of the router is local to the remote server and not visible to ping from anywhere else.
From my application I want to do this in code but I don't know where to start (been searching for a while).
I am not asking for the code I just want to know what I should be looking at.
using a scheduled task as #Nkosi pointed in his comment is not a bad idea, but the most professional and stable way is to write a windows Service that will handle this task. a service is different than a process, its always runs on the background and NT User is not have to be logged in. you can setup timers to schedule the pinging inside the service application. Creating a Windows Service Application

Which is Best For Hosting My Vb.Net Windows ERP Application

I have a windows server 2008 and sql server 2005 and my application is windows based.
I have created a wcf service in my application for sending SMS.
I have a server with internet connection and have 50 pc's in the network.
They dont have internet connection, but they want to send sms through server.
I made the wcf service for sending sms. This service is working good on server.
Which hosting is best for my application ?
How to access this service on client machine ?
In IIS
Using a pre-generated proxy or at runtime using ChannelFactory

What rights are required for IIS to talk a WCF service hosted on a different machine?

In this question: ASP.NET web application unable to connect to WCF hosted as windows service
it's stated that the reason IIS could not talk to a WCF service hosted on a different machine is due to rights not assigned the app pool identity.
I'm facing the same problem I believe. What are these rights, and where do I set them?
Thanks.
This depends on the configuration of the service you're trying to access. However, if you're having trouble connecting to a different machine, you most likely don't have rights to access that computer using the machine account for the server hosting IIS. You could try adding [domain][iismachine] access to the target server (the one hosting the WCF service).
This overview has some pretty good information on what needs to be done in different scenarios.

Difference between web server, application server and database server

I read somewhere that a web application consists of a web server, application server and a database server. What is the difference between these three ?
I asked this question because I remember when I hosted a website, all I had was a https login to the control panel of the website, in which I put all my files in htdocs folder. There were no three separate things like the web server, application server and the database server.
This often gets confusing.
Firstly - "Server" can refer to a physical thing (a computer), or a logical thing (a piece of software).
Web, application and database server software can all run on the same physical server machine, or be distributed across multiple physical machines. Most large websites have multiple machines; most "consumer" hosting packages run on a single box.
The logical separation is as follows.
The Web server deals with HTTP(S) requests, and passes these requests on to "handlers". They have built-in handlers for file requests - HTML pages, images, CSS, JavaScript etc. You can add additional handlers for requests that they cannot manage - e.g. dynamic pages delivered by the application server. Web servers implement the HTTP specification, and know how to manage request and response headers.
The application server handles requests which create dynamic pages. So instead of serving an HTML page that is stored on the hard drive, they dynamically generate the HTML sent to the end user. Common languages/frameworks for this are Java/JSP, .Net (aspx), PHP, Ruby (on Rails or not), Python etc. Most of the time, this application server software is running on the same physical server machine as the web server.
The database server software is where the application stores its structured information. Typically, this means custom software which allows the application server to ask questions like "how many items does user x have in their basket?", using a programming language. Examples are MySQL, SQL Server, Oracle (all "relational databases"), and MongoDB, Redis and CouchDB ("NoSQL" solutions).
The database software can run on the same physical machine as the web server, but it's usually the first thing that gets hosted on separate physical hardware when the site needs to scale.
Web Server -
Server on which your website is hosted. This server will have installed web servers such as IIS, apache, etc.
Application Server -
Server on which your created applications which are utilizing your database, web service, etc.
This application server will host business layer (wrapped with web services), scheduled jobs, windows services, etc.
Database Server -
Database server will have your one or more database hosted such as Oracle, Sql Server, MySql, etc.
If you are referring to htdocs then it is a Web Server. The database you are using is must be installed on different server which is your Database server. Application server can also be installed on the same web server machine.
Reference - Deployment Patterns
Web Server: The server on which all your HTTP requests are handled is known as a web server
where as
Application Server: Including the services of web server i.e responding to the HTTP requests it also responds to the business logic thus not just limited to the HTTP protocol
Eg. gaming servers, chat rooms etc.

Alternate Access Mapping not working in SharePoint 2010 Workgroup

I have tried to configure alternate access mappings in my SharePoint 2010 which is installed in WorkGroup Windows Server 2008 R2 server but could not make it work.
Here are my steps.
Go to Central Administration-> Manage Web Application.
Select a web application and extend it.
Provide the my12server.com in the host header and leave other default values as it is. I changed the zone to Extranet.
Click Ok.
After sometime, it creates Web Application in SharePoint and Web Site in IIS.
I have changed my hosts file by adding entry
192.168.1.11 my12server.com
Browse the new extended. It asks for credential. Supplied the correct credential but nothing got display. Just a blank page.
Note: I have however successfully extended web application when the SharePoint 2010 is in domain machine.
Please advice me.
Thanks
Prakash
SharePoint is designed to work in domain environments only. In other words, you cannot expect to run it on an underlying Windows Server which joined into a workgroup and expect full functionality. Although there are blog posts around describing installation in a workgroup environment (or, better to say, using local accounts), I wouldn't recommend wasting time with such a mode of operation.
Furthermore, it doesn't make sense to extend a web application just for the sake of providing another hostname. Extending web applications multiple times is mostly useful when you need different authentication providers for each of them. In your simple case you can just configure multiple Alternate Access Mapping records for a single web application.