Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I Have all the hosting details and Domain specifications, I have logged into ftp using ftp details now where to upload the files of my website to make it work?
Generally in C:\inetpub\wwwroot\. However, I highly suggest you research a lot more on the topic if you're going to be managing a web server.
You should become familiar with IIS and IIS management. In windows server 2008, You can use Server Manager to add the IIS Web Server role if it doesn't already exist. Then you should expand Roles and Web Server (IIS) to reveal "Internet Information Services (IIS) Manager". That is where you set up the web server. Explore the menus there, they provide options you will need. Enjoy!
If you have a domain name and FTP details, sounds like you're using shared hosting. In that case, often the FTP directory will have "httpdocs" in it or "wwwroot", or maybe even "public_html". You place a file there and it should be accessible through the domain. Of course it might also be the case that you will need to change your nameservers on the domain to the nameservers that the hosting company provided.
Whenever I work with a new hosting company, I always do a test with a simple "test.jpg" (no scripting, no PHP, no ASP, etc). Once that works through the URL that I expect, I start more complicated tests.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I want to disable external access to ECP Exchange 2016. How to do it?
I will read main step for solution.
Run the Add Roles and Features Wizard from the Exchange Server. Select your Exchange Server and follow the wizard. Now you are on the Server Roles tab. Expand Web Server (IIS) -> Web Server -> Security. Check the IP and Domain Restrictions role. On our end, it’s already installed on the Exchange Server.
Click on Next. Click Install to install the IP and Domain Restrictions role. Installation completes. Proceed further with the steps below.
Open IIS Manager on the Exchange Server. Expand Server -> Sites -> Default Web Site. Select ecp. Double click on IP Address and Domain Restrictions.
The IP Address and Domain Restrictions feature is open. Let’s configure it to disable external access to ECP on the Exchange Server 2016. First, click on Edit Feature Settings… and configure it to Deny access for unspecified clients. Set the Deny Action Type to Not Found.
Click on Add Allow Entry… and configure that you can access ECP internal on the Exchange Server (localhost). Add the IP 127.0.0.0 with prefix 8. If you want to add the subnet mask instead of the prefix, it should be 255.0.0.0.
You added the entry. Now you can log in ECP from the Exchange Server, go to https://localhost/ecp. I don’t recommend to open ECP on the whole internal LAN. If you have management servers, add the IP addresses to the allow list.
You added the entries and it is showing correctly. Start ECP and login from the IP addresses that you added. Make sure you insert the Exchange Server hostname. For example, https://EX01/ecp.
Source: https://www.alitajran.com/disable-external-access-to-ecp-exchange-2016
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I'm developing a web application for use inside our internal Windows domain. I have 3 servers: apps.mycompany.com (primary), api.mycompany.com, and files.mycompany.com. Right now, everything works fine over HTTP. But I need to have these accessible over SSL/https to Windows desktop clients on the network (Chrome/Firefox/Edge) and iOS (Safari/Chrome).
I've set up self-signed certs using OpenSSL, and have configured nginx to where they respond correctly, and serve data. But, I'm constantly running into "not secure" / "invalid certificate" errors and "mixed content" (http/s) warnings that stymie my development. The errors on api and files are especially pernicious, as they just "break" things not obvious to the user.
I need a solution where everyone can simply hit https://apps.mycompany.com... and everything "just works", without user intervention (allowing insecure connections, manually adding certs, adding certificates to Trust stores, etc.)
Advice?
EDIT: I see this question was closed. Isn't setting up SSL/https an integral part of modern web development? (and yes, I had already asked my question on Server Fault).
You need to create a root certificate that would be trusted by all your clients. Then you can sign server certificates with that "root" key so that server certificates would also be trusted.
This is the example how you can issue such certs.
More challenging task is to install this root cert to all your clients. You can ask your domain administrator to help you with that. Otherwise you will have to ask all your users to install that root cert (they will also probably have to be local administrators..)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I have To create a spring batch which have To connect on remote server ( nginx) and get list or files and download on local server for treatment.
There is no API
How To do that in the best way ?
Ftp ?
Thanks
If you already have an FTP server running, you could use Apache Commons Net API to download files as shown here. However, depending on your exact scenario, FTP might be insecure.
As an alternative to FTP, WebDAV comes to mind, which is based on HTTP(S). I have used sardine for uploading files to an apache httpd server from a Spring Batch client. I haven't set up WebDAV on nginx myself yet, but you can find quite detailed instructions on the web.
Or if an sshd is running on the server, you could either use JSch to transfer the files via SFTP as described in this tutorial or use spring-integration-sftp (which also uses JSch under the hood).
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
i have some problems configuring the outlook client for dynamics crm 2011. the crm-server runs on a dedicated server, that is not rechable from outside the network of my company (im using dynamics crm for my master thesis). i can only reach it from within our network and i have no problems to do so with the internet explorer and the web client.
when i start the config wizard of the outlook client, i am prompted to insert the url of the crm-server. when i type in the ip of it (including the port where the crm-server is installed), i get the response, that there is no communication possible (to the server).
i also tried to change the windows hosts-file and resolve the dns/server-name to put the servername into the field (instead of using the ip). but nothing can bring me further in the wizard. i cannot sign in to dynamics or select an organisation.
greets,
suutsch
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm going to have my website hosted soon on a VPS or dedicated server (with Windows 2008), so I'm trying to plan ahead. I wonder whether the built-in SMTP server that comes with IIS7 is reliable enough for a production server or should I look for an alternative? I heard good things about hmailserver and best of all it's free, do you have any experience with using the bulit-in SMTP on a high traffic website.
Thanks a lot for any suggestions
I hit this thread via Google but I was looking for an outbound only SMTP server for transactional emails (customer registration confirmation etc. but not marketing), then some things I discovered are:
SMTP does still exist in Windows Server 2008.
Server Manager > Features (not Roles) > Right-click, Add > SMTP Server - then Configure IIS 7 SMTP to point to the local server.
Then use the Framework to do the business: http://msdn.microsoft.com/en-us/library/system.net.mail.smtpclient.aspx
Jango have a paid for but cheap enough service for exactly this kind of thing. The Free account only allows 200/month but might be useful for some folk.
http://www.jangosmtp.com/Pricing.asp
Good luck!
UPDATE
I blogged about setting up the original MS SMTP Server on Windows Server 2008.
http://www.lukepuplett.com/2010/06/how-to-send-email-from-microsoft-server.html
hMailServer. Free and open source.
At work, we used to use the SMTP server in IIS 6.0 for years and it was perfectly fine.
Eventually, we just simply didn't want all the issues that come with running your SMTP server so we mapped our MX records to a third-party service and moved on with our lives.
It's not actually that bad an idea to map your MX records to a third-party provider, like Google. It's one service less to configure and one service less to patch.
This is an old post but I thought I'd make a recommendation since this does seem to come up frequently.
In my opinion you should try to avoid running mail on your VPS/Dedicated Server if you can. It's one more thing to manage and one more headache. My recommendation would be that use a 3rd party service like sendgrid.com that will allow you to relay mail through them. This way you won't have to worry about your new server getting blacklisted or being seen as having a low reputation score and your messages not making it out of the user's spam box. The other issue is that when you setup your mail server, you need to secure it and you need to make sure it's got a reverse DNS entries, many providers won't provide that and/or they'll recycle IP addresses so that the IP address of your server actually has a poor reputation.
What about xmailserver (as suggested in this SO question) ?
It is free, and for Windows or linux (should you migrate on a linux server platform)
(source: xmailserver.org)
Being on windows, your best choice will probably be IIS.
If it was Linux, I'd suggest postfix.
you haven't mentioned if you are needing to receive mail, or just to send it.
One of the best all around solutions for a windows mail server is IpSwitch's iMail (http://www.ipswitch.com/), but it costs.
If you mainly need to send mail, then your best bet is to use an upstream smtp server.
IIS smtp services are, in general, not useful. If you use Exchange, it gets a bit better, but still not very efficient, and not the most secure by any means.
Maybe sending it via gmail is a good one :P
Ok serious. IIS7 seems I heard to have some decent improvement. If that's not doing it, I guess you could try free stuff like mailenable.
(No I can't find the evidence on the improvement on IIS SMTP, people who know about this please comment)
Long term you might end up split it to a linux based smtp though, that gives you some flexibility on server farming if it goes too insane.
And if its for any kind of mass mailing that might trigger spam server blocking, don't ever try to host it together with your other important stuff- you want to keep yourself have a back step if your server gets blocked.