from home Pinger showing everything ok, however email or putty unable to connect.
isup.me showing email.nmlindia.org as ok. Found redirection/reverse proxies working. But putty through BSNL ip not working. email.nml.in is working without any problem.
Looks BSNL has some problem.
After login to ldap1 with nkn ip did the following:
checked local accessibility to port 80
[root@ldap1 ~]# telnet 117.239.23.228 80
Trying 117.239.23.228…
Connected to 117.239.23.228.
Escape character is ‘^]’.
GET / HTTP/1.0
HTTP/1.1 302 Found
Date: Fri, 04 Dec 2015 03:04:31 GMT
Server: Apache/2.2.8 (Fedora)
Location: https:///
Content-Length: 270
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href=”https:///”>here</a>.</p>
<hr>
<address>Apache/2.2.8 (Fedora) Server at email.nml.in Port 80</address>
</body></html>
Connection closed by foreign host.
ITS OK.
[root@ldap1 ~]# ping -I 117.239.23.228 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 117.239.23.228 : 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=43.3 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=43.5 ms
— 8.8.8.8 ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 43.324/43.450/43.576/0.126 ms
NO ISSUES
tried following from the home
C:\Users\Byomkesh>tracert -d 117.239.23.225
Tracing route to 117.239.23.225 over a maximum of 30 hops
1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 29 ms 29 ms 29 ms 117.239.23.225
Trace complete.
OK no Issues
C:\Users\Byomkesh>telnet 117.239.23.228 80
Connecting To 117.239.23.228…Could not open connection to the host, on port 80: Connect failed
BUT telnet 117.239.23.245 80 WORKING
Looks a firewall issue. But did not work even on stopping the FW. to be checked at office.
Surprised no issue when accessing email.nmlindia.org via http://www.locabrowser.com/ and country jp,sg, uk,ca,fr,de
or using http://network-tools.com/default.asp?prog=httphead&host=117.239.23.228
ITS DEFINITEY A BSNL BOADBAND ISSUE I HAVE NO IDEA WHO in BSNL WILL UNDERSTAND AND RESOLVE. somewhere they are blocking traffic from BB to our IP
————
Many people (like Rakesh) still reporting problem in NMLN connectivity. Check radius radius2 APs found no problem. Many users are connected and working without problem.
Later found Disk space problem in logserver (it was full). Since it has a 6 GB hda need to upgrade to higher. for the time being deleted the /tmp contents, freed 1GB then rebooted.