Executing a ping from a remote server - vb.net

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

Related

Windows Integrated account is slow to connect to the SQL server database.

I have a SQL server that belongs to a domain and an application server that is stand alone. Of course it has the right ROUTES to reach the sql server.
when I use a test.udl file to test the connection, a sql login would work right away. But if we try a windows integrated account (servername\username) it takes about 25 seconds to connect.
Unfortunately I have MSMQ running on that server and application that has to take these messages and send it to the SQL server. Because of the delay (I think) MSMQ keeps all its messages.
Do you know what could be the reason for this delay only on WIndows integrated logins?
Note that, I have windows firewall disabled on these servers, No Antivirus.
SQL Server 2008 R2.
Application Server - Windows 2008 R2
Thanks for your time,
RM

SSIS & Business Objects SDK Error: File Repository Server Input is Down

Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.

windows 2008 server R2 - remote desktop crashed after recent update

I have updated the server recently (only those recommended security update from the windows server), after installation i had to restart the windows server, however after restarting the server, all the port are closed and I have no access with RDP (no access to sql server database, no access to tfs ...) .  currently i can access to the server only over the ssl and i have access only to the cmd consul on the server. can any body help?(the server is in the ISP and it is a dedicated server).
Cause:
installation first kb2667402 then the Sp 1 update
effect:
No RDP available
Windows blocks users right and give no right to start the services
e.x
The TFS Service uses TFSSERVICE USER, but win2008r2 block this user and say this user is not exist!
what we have done:
uninstall the kb2667402
after Uninstalling the kb2667402, i have exported the installed update and proved that the updated has been successfully removed.
delete and copy the old version of the rdpcorekmts.dll in system32
reconfiguration of the RDP and add a new port and rule for firewall
reset the firewall and add the new rule (we made a back up)
add the Teamviewer portable version with a fix password, but we cannot access to the TV, "Authentication rejected"
Installed RAdmin--> no access: the user name or password is wrong!
try to connect with Computer management from my pc to the server and get the error: RPC Sever is Unavailable
I have stop the firewall and had access from my pc Event Viewer to remote server and could follow the errors on the server.
Problem reported
http://support.microsoft.com/kb/2667402
http://tmkilla.com/2012/04/windows-server-2008-r2-rdp-connection-error-sp1-kb2667402/
I have tried all the thing but didnt solve the problem. an idea how to solve the problem?

Web services dilemma

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?

What is the correct way to install Celery/Redis to run the tasks on another server?

The web server itself runs django. I would like the web server to delegate the actual tasks work to another server.
First, setup your redis server on the remote server. Change your django configuration to connect to this server.
When you deploy your app, I recommend using fabric to deploy to your web server and your worker server. It should handle the restart logic as well.