How do I bind to just one IP address with VisualSVN Server? - apache

I've installed VisualSVN on my Windows Server 2008. I have several IP addresses on this server, but I want VisualSVN to only bind to one of them. By default it binds to all available addresses. How can I make VisualSVN only handle requests on one IP address?
I tried adding
BindAddress xxx.xxx.xxx.xxx
to httpd-custom.conf and restarting the service, but that didn't seem to work.
I tried the same with httpd.conf, and it didn't work either.

To clarify, the method for binding VisualSVN to explicitly defined IP addresses is:
Load the VisualSVN Server Manager MMC snap-in
In the left pane, right-click the VisualSVN Server item and choose Properties from the context menu
Click the Network tab
In the Server Binding group, select the radio button for These IP addresses
For each IP address you want to specify:Click the Add... button
Enter the IP address in the text box and click OK

I found an easy way! I just upgraded to VisualSVN 1.6. Then, in the management console, right-click the VisualSVN Server node, select the Network tab, and enter your IP address(es). Cool!

Related

How to restrict in VisualSVN Server access only to some specific public IPs

I have connected an USB network adapter on the Visual SVN server and configured a public ip on it. Now, the repositories are accessible though an https link over the Internet to everyone who knows about the link.
I want to allow the SVN access only from our US office (I have the public ip of US office). People from any other location or public ip should not be able to access the SVN. The VisualSVN server is setup on a Windows 10 machine. IS this possible on Windows? If yes, can someone please tell me how.
First of all, you can adjust Windows Firewall rules to deny certain clients to access VisualSVN Server based on their IP address. This is the approach we at VisualSVN suggest at the moment.
On the server computer, follow these steps:
In the Control Panel, click System and Security and then click Windows Firewall.
Click Advanced settings.
In the list of inbound Firewall rules locate VisualSVN Server (TCP-In) rule and double click it.
Select Scope tab.
Specify IP address under Remote IP Address. The Firewall rule is configured to "Allow the connection" by default. Therefore, this list contains the IP addresses allowed to access VisualSVN Server. Unlisted IPs are not allowed to access VisualSVN Server. You can adjust this behavior on General tab in Action section.
For more information about editing Windows Firewall rules, please read the TechNet article "Add or Edit Firewall Rule".
Regarding the suggestion by #LazyBadger: indeed, is possible to implement IP-based restrictions via modifying httpd-custom.conf file, however we strongly discourage to take this approach. VisualSVN Server has SVNPathAuthz short_circuit option enabled, which dramatically improves
authorization performance. The option has a limitation, though: server
configuration mustn't rely on other authorization modules such as
authz_host_module (which is responsible for IP-based checks),
otherwise you will encounter unexpected behavior with authorization.
On the other hand, if you disable short_circuit you will definitely
notice performance degradation when running authorization-intensive
operations against you repositories (such as running svn log, svn checkout, svn export etc or running a graphical repository browser
such as the one TortoiseSVN client provides).
So the recommended way to apply such IP-based restrictions is to use
firewall settings.
VisualSVN Server is Apache behind the scene - all tasks, not related to SVN directly, are managed by Apache and it's possibilities
You have to use Apache's Access Control in form like
Order deny,allow
Deny from all
Allow from us.ip.address
You have to check, if mod_authz_host for the above trick is enabled (re-read LoadModule section in httpd.conf)
Don't touch main httpd.conf with your modification (it will be lost on update server), add your customization into %VISUALSVN_SERVER%conf\httpd-custom.conf file

How to use IP instead of localhost

I am using Windows server 2008 and installed wamp on it. Now I want to share the local link with client using same network.
Instead of [localhost], I am trying [server_ip_address]. but it's giving me error.
I want to use it as 192.168.30.1 but not able access this.
I also put the wamp online and restart the server. I m able use the ip from my m/c only. If I use this link from another m/c then its giving following error
URL http://192.168.5.12:8080
Error The connection has timed out
you can access the Server from your clients with url like,
http://server ip address : port
Your Local clients and your Local server must be connected in a LAN network.
Check your Windows firewall settings. Check by turning off the private network firewall

Unable to ping from the SQL server in Azure

I have 3 VMs in Azure, one of them is DC and DNS, the other one is going to be SCCM, the ther one is SQL server.
I joined the two VMs to my DC. They have correct IP config. One of them is just fine. I can ping DC from the SSCM and vice versa.
But from the SQL server I cannot ping. nslookup does not work correctly either, but the IP config is correct.
Does any one know where is the problem?
Note: DNS server is fine. Also, I have records in DNS server that are pointing to SCCM and SQL.
Ping is disabled by default on the Windows Server VM's. Sign-in to the VM you want to ping and open the Server Manager (icon in the lower left corner).
In the upper right corner where the menu is, select Tools -> Windows Firewall with Advanced Security. Click on the Inbound Rules in the left navigation, locate the File and Printer Sharing (Echo Request - ICMPv4-In) rule. Right-click on it to enable it.
Now you should be able to ping it from other VM's in your Virtual Network.

how to access local web application on glassfish server from internet?

I have created a web application in glassfish and I can access it on my LAN.
How can I access the web application from a remote location over internet?
I do not have static IP.
Please reply.
Thanks.
Steps :
Creating virtual DNS(Domain name server) Server on your machine.
Port Forwarding.
Reference https://cookbook.fortinet.com/port-forwarding-60/
Remote Desktop Connection enabling.
Creating Inbound Rules. Reference :
https://www.howtogeek.com/112564/how-to-create-advanced-firewall-rules-in-the-windows-firewall/
Creating account on www.noip.com and create custom host and download DUC (Dynamic Update Client) Software.
Some more steps may have it depends on your LAN Router and firewall configuration.Use http://ifconfig.me/ to get your public ip.
Access from outside your machine should be configured by default. You may check if it is so in admin console, at Configurations->server-config->Network config->Listenters. There should be one listening on the desired port (like 8080) and be bound to 0.0.0.0 address.
To easily access something behind a dynamic ip you need something like http://www.noip.com/ or http://www.dnsomatic.com/ (I took these from my router's control panel)
I did this recently,
first you need to use port forwarding on your router, access it by typing your default gateway path, mine was 192.168.0.1 then go to "advanced settings -> Port forwarding". Simply enter the details that are asked for, I set mine to HTTP using port 8080, yours might be different. Protocol is TCP. The IP address it asks for is your local address.
For quick testing you can disable the firewall on your machine and then you can search on google for your Public IP address by typing "what is my IP".
Then type your ip into the browser and the port number "ipAddress:portNumber"
You should see the glassfish welcome screen if it is successful.
After that you might want to enable your firewall again but then you have to add an inbound rules to allow the port to be used:
Setting Windows inbound rules
Then you still have one last step to perform, allowing glassfish to access the resources on your machine: Adding glassfish to allowed programs
Follow the instructions on adding java.exe only.

How do I Change IIS Express 8 port 80 to 8080

I used to use vs2010 and webmatrix. However,I'm trying to use apache lately.
So my IIS express is using port 80 and apache is using port 8080.
I intend to have it the other way around. Let apache use port80 and IIS use 8080.
I couldn't let apache listen to port 80 until IIS no longer listen to port 80.
How should I config IIS express's port?
ps.I'm using win7 with one ip adress
Try this
To configure the default IIS website to use port 8080
On the Windows desktop, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
In Internet Information Services (IIS) Manager, in the Connections pane, expand the computer name, expand Sites, and then click Default Web Site.
In the Actions pane, under Edit Site, click Bindings.
In the Site Bindings dialog box, click the http entry, and then click Edit.
In the Edit Site Binding dialog box, in Port, type 8080, and then click OK.
In the Site Bindings dialog box, click Close.
In the Actions pane, under Manage Web Site, click Stop, and then click Start.
Microsoft Internet Information Services 7.0
1. Open Internet Information Services (IIS) Manager. Select the Web.
2. site that you wish to configure. In the Action pane, click Bindings.
3. Click Add to add a new site binding, or click Edit to change an existing binding.
4. Click OK to apply the changes.
Source - How to change the port for IIS services
How to change IIS port in windows
Posted on November 21, 2017 by Suresh Kamrushi in Windows
[Like] +2
[Unlike] 0
Thanks for your vote.
Showing here, how you can update IIS server port number in windows 10/8 system. There may be several reason you want to change the port but for me its WAMP, I am using it for PHP projects. IIS and WAMP use same port which make trouble developing. So I updated IIS port. You can also update the WAMP port, referring to my blog
Follow the below steps to update IIS server port number:
Go start and type IIS
IIS Manager will open. click on “Default Web Site” on left hand side.
click on “bindings…” from the right side action section.
Popup will open with 80 port listed. select it and click the edit button.
Update the port and restart the server.
source : http://sforsuresh.in/change-iis-port-windows/
IIS 8.1
Select “Default Web Site” from the left tree in IIS manager.
Click Bindings from the right sidebar to open a dialog box.
Select “http” record from the grid and hit Edit.
Enter your choice of port number in “Port” Text box and hit OK.