How to Prevent Nmap , Displaying HTTP Header Details - iis-8

I have
OS: Windows Server 2012
IIS 8.0.
I Used MicroSoft's URLRewrite 2.1 For hiding HTTP Server Details.
Its working fine for Firebug(Firefox) , Developer Tool (IE).
But When i Fire Below Command in Nmap , It shows all Details related to that server.
Command : nmap -sV -p 443 172.16.40.45 172.16.4.45
Please Help.

Related

Attunity Replicate sample installation

I am trying to install Attunity Replicate into a local virtual machine with CentOS 7 on it. I can see that it is running - using 'ps -ef | grep repctl', and I know that the 3552 port is open in the firewall, and the host is visible (using 'nc -zv 3552').
But I cannot connect my UI browser to Attunity server using 'https://:/AttunityReplicate' - the Safari answers that 'Safari can't open the page XXX becauseSafari cannot establish a secure connection to the server...', and Chrome answers with 'ERR_SSL_SERVER_CERT_BAD_FORMAT' error...
Any hints - what and where should I configure in the Attunity Server to resolve the security issue, please?
Kind regards,
Alex
On the Linux server where you installed Replicate Express, cd into /opt/Attunity/replicate/bin (this is the default location) and run the following command:
cd /opt/attunity/replicate/bin
source arep_login.sh
./repctl SETSERVERPASSWORD
./arep.ctl stop
./arep.ctl start
Ensure that your Linux server allows inbound TCP connections on port 3552
Open your browser and try to connect to the following URL: https://:3552/attunityreplicate replacing with the DNS name or IP address of the Linux Server where Replicate is installed.
When prompted, enter the Username: Admin and Password from Step 1.
You may have to allow the webpage on Chrome:
1- On your computer, open Chrome.
2- On the page where you see a warning, click Details.
3- Click Visit this unsafe site.
4- The page will load.
Reference: https://support.google.com/chrome/answer/99020?co=GENIE.Platform%3DDesktop&hl=en

- Restcomm Olympus WebRTC WSS error,

We are trying to use RESTCOMM OLYMPUS by making few customizations as part of our application. The main customization is that we have deployed OLYMPUS war on our Apache TOmcat web server and the OUTBOUND PROXY is properly pointed to the same server where RESTCOMM is running.
So far all is good, but recently we got the issue that "getUserMedia()" deprecation issue because of insecure origin issue by chromium fix.
So, it means we need to use HTTPS and WSS. I can see that just around 7 days back OLYMPUS code has been updated on GITHUB to use WSS if HTTPS has been used in browser location bar.
So first we have installed self signed CERT and enabled SLL config on TOMCAT so that our customized OLYMPUS UI is accessed via https from Tomcat. And then we used WSS protocol to connect to OUTBOUND PROXY. Bt we got the below error
"WebSocket connection to 'wss:/:5082/' failed: Error in connection establishment: net::ERR_TIMED_OUT
WSMessageChannel:createWebSocket(): websocket connection has failed:[object Event]"
Then we thought that in addition to TOMCAT ( where WAR is deployed) we need to install self singed cert and SSL config on RESTCOMM as well. So we did it by following http://docs.telestax.com/restcomm-enable-https-secure-connector-on-jboss-as-7-or-eap-6/ and also we have used WSS protocol.
But this time also we got the error but with a different error code though
"WebSocket connection to 'wss:/:5083/' failed: Error in connection establishment: net::ERR_CONNECTION_CLOSED
WSMessageChannel:createWebSocket(): websocket connection has failed:[object Event]"
Can i request the forums to explain if we are missing any thin here?
Thanks in advance
I would suggest to use the mobicents RestComm docker image instead of using the zip bundle, because for docker image all settings are handled automatically and https/wss should work out of the box. Here are some quick steps to get you started:
Install docker in your Ubuntu if not already there
Download RestComm docker image:
$ docker pull mobicents/restcomm:latest
Start docker image:
$ docker run -e SECURE="true" -e SSL_MODE="allowall" -e USE_STANDARD_PORTS="true" -e VOICERSS_KEY="VOICERSS_KEY_HERE" --name=restcomm -d -p 80:80 -p 443:443 -p 9990:9990 -p 5060:5060 -p 5061:5061 -p 5062:5062 -p 5063:5063 -p 5060:5060/udp -p 65000-65535:65000-65535/udp mobicents/restcomm:latest
Now you should be able to reach your RestComm instance Admin UI at:
https://<host ip address>/
Make sure that you don't have any servers running in your host at the ports used by the docker container above, or you'll have to use different ports (please refer to the docker hub page for such options)
Best regards,
Antonis Tsakiridis

How to run Tomcat on Linux (which has glassfish on port 8080)

I am trying to run to tomcat on linux where glassfish is already running on port 8080 ( you can check here - vhost2.cs.rit.edu:8080 . So i changed the tomcat port to 8181 by editing the server.xml file. NOw with the command startup.sh and i get the following output
Using CATALINA_BASE: /home/krs8785/apache-tomcat-7.0.54
Using CATALINA_HOME: /home/krs8785/apache-tomcat-7.0.54
Using CATALINA_TMPDIR: /home/krs8785/apache-tomcat-7.0.54/temp
Using JRE_HOME: /usr
Using CLASSPATH: /home/krs8785/apache-tomcat-7.0.54/bin/bootstrap.jar:/home/krs8785/apache-tomcat-7.0.54/bin/tomcat-juli.jar
Tomcat started.
I am assuming that tomcat is now working. Now when i test the server by - vhost3.cs.rit.edu:8181 I get
No data received on the browser.
What is the problem here and how do i solve it?
The problem may be unrelated to tomcat. I think your first step should be to exclude networking issues.
I have assumed you are accessing vhost3.cs.rit.edu:8181 from another machine. If that is the case, try to access localhost:8181 from vhost3.cs.rit.edu. If this is not possible in a conventional browser, perhaps because it is a headless server with X forwarding disabled then use a terminal based browser. Try typing the following in the terminal on vhost3.cs.rit.edu
lynx localhost:8181
If you are able to see a representation of a tomcat splash page then you can attribute it to networking issues. This could be firewall related (perhaps even an issue with iptables on linux).

Installing httpd-2.4.3 in RHEL 5.3

I have installed httpd-2.4.3 on RHEL 5.3. I followed the basic installation which later then it runs on
/usr/local/bin/apachectl restart -f /usr/local/conf/httpd.conf
I can access locally (just use telnet localhost 80) , but i cannot access from remote using my browser or telnet port 80 from other server.
adding port 80 to IPtables, - done
httpd services is running - checked
Thanks for the reply.
Check your /etc/selinux/config is enable or not.

Apache service failing ("BUSY") when using port 80 [closed]

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 9 years ago.
Improve this question
How can I configure my Apache server to run on port 80? My Apache service is failing when using Port 80; it says BUSY.
When I change the port in config to 85, Apache works but this requires maunally entering 85 in the address bar every time with localhost.
I have tried to find out which program is using port 80 but I cannot come up with anything. I first entered netstat -n -a -o -p TCP in cmd and I came up with this information
Local Address 0.0.0.0:80 State: Listening PID: 4
Then I entered tasklist in cmd trying to figure out which service is using this port. Looks like "System" is on PID 4. I have configured Skype to not use port 80 without any luck. I have Microsoft WebMatrix installed on Windows 7 and I even deleted IIS 7.5 Server Express to free this port but all to no avail.
Can you guys please help me out? I am using Windows 7 and XAMPP.
Several programs can block that port. Candidates are:
Skype
Web Deployment Agent Service (can be stopped via Start -> [-> Run] -> services.msc)
World Wide Web Publishing Service
IIS (if you have it installed)
TeamViewer
VMware (in VMware Workstation go to Edit>>Preferences>>Shared VMs, and Disable Sharing or change the port)
Web Deployment Agent Service and World Wide Web Publishing Service can be set to manual start to keep them from running. Stop or change these services from an account that has administrator permissions.
Skype and TeamViewer can be configured not to use port 80.
For Skype Go to Options > Advanced > Connection and un-check "Use port 80 and 443 for incoming connections"
For TeamViewer Go to Extra > Options > Advanced and un-check the similar message as above.
EDIT: I made the post a community Wiki, so if people find other programs, they can add them here.
For me, it turned out to be that "Web Deployment Agent Service" was taking port 80. As soon as it was disabled apache started right up. I've also come across quite a few saying some of the SQL Server services were blocking it.
EDIT:
Just thought I'd add that the new MSN(Skype) causes this as well, using port 80 by default. It can be changed in the settings:
Tools > Options > Advanced > Connection > Untick "Use Port 80 and 443" > Save
You can also just change the port the Apache Web Server is using in the httpd.conf file.
In a Windows OS command prompt I use;
netstat -an
to see what services are already running, and what ports they are using, then just pick a port number that's not being used. Much simpler. That's for my Dev environment. On an actual server or in the cloud, I would run the Apache Web Server without conflicts and just shutdown anything else that happens to be using port 80.
I’m currently beta testing the next version of Windows, Windows 7 and came across a strange issue while trying to get Apache to install and run using the default port, 80.
Running the command ‘netstat -ano’ from the command line revealed
that port 80 is being used by PID 4.
Looking up PID 4 using Power Shell and then Task Manager revealed
that PID 4 is the NT Kernel!
So Windows 7 by default appears to be using port 80.
After a bit of hunting around the Internet and doing some research of my own I found that the service http.sys was the culprit and all I needed to do was disable it but I could not find this service listed in the Services control panel applet.
So what’s the solution?
You have to disable the http.sys service manually via the registry:
1) Launch RegEdit:
2) Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
3) Add a new DWORD (32-bit) value
4) Name it ‘NoRun’ not including the quotes
5) Double click the new property
6) In the Value data field type ’1′ not including quotes and click OK
7) Re-boot your computer
You should now find that Apache will start on port 80!
Oh, thank you a thousand times. I've been wrestling all day with getting port 80 free. Tried everything that I found on the chat rooms, forums, including the regex edit above, and still there was:
netstat -ano -p tcp | findstr LISTENING
TCP 0.0.0.0:80 0.0.0.0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0 LISTENING 4 etc.
Now port 80 has disappeared from the display. What a relief!
Just thought I would put my input in:
I stopped service MsDepSvc (AKA: Web Deployment Agent Service) and this solved the issue.