from home Pinger showing everything ok, however email or putty unable to connect.<\/p>\n
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.<\/p>\n
Looks BSNL has some problem.<\/p>\n
After login to ldap1 with nkn ip did the following:<\/p>\n
checked local accessibility to port 80<\/p>\n
[root@ldap1 ~]# telnet 117.239.23.228 80
\nTrying 117.239.23.228…
\nConnected to 117.239.23.228.
\nEscape character is ‘^]’.
\nGET \/ HTTP\/1.0<\/p>\n
HTTP\/1.1 302 Found
\nDate: Fri, 04 Dec 2015 03:04:31 GMT
\nServer: Apache\/2.2.8 (Fedora)
\nLocation: https:\/\/\/
\nContent-Length: 270
\nConnection: close
\nContent-Type: text\/html; charset=iso-8859-1<\/p>\n
<!DOCTYPE HTML PUBLIC “-\/\/IETF\/\/DTD HTML 2.0\/\/EN”>
\n<html><head>
\n<title>302 Found<\/title>
\n<\/head><body>
\n<h1>Found<\/h1>
\n<p>The document has moved <a href=”https:\/\/\/”>here<\/a>.<\/p>
\n<hr>
\n<address>Apache\/2.2.8 (Fedora) Server at email.nml.in Port 80<\/address>
\n<\/body><\/html>
\nConnection closed by foreign host.<\/p>\n
ITS OK.<\/p>\n
<\/p>\n
[root@ldap1 ~]# ping -I 117.239.23.228 8.8.8.8
\nPING 8.8.8.8 (8.8.8.8) from 117.239.23.228 : 56(84) bytes of data.
\n64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=43.3 ms
\n64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=43.5 ms<\/p>\n
— 8.8.8.8 ping statistics —
\n2 packets transmitted, 2 received, 0% packet loss, time 1000ms
\nrtt min\/avg\/max\/mdev = 43.324\/43.450\/43.576\/0.126 ms<\/p>\n
NO ISSUES<\/p>\n
tried following from the home<\/p>\n
C:\\Users\\Byomkesh>tracert -d 117.239.23.225<\/p>\n
Tracing route to 117.239.23.225 over a maximum of 30 hops<\/p>\n
1 2 ms 2 ms 2 ms 192.168.1.1
\n2 * * * Request timed out.
\n3 * * * Request timed out.
\n4 29 ms 29 ms 29 ms 117.239.23.225<\/p>\n
Trace complete.<\/p>\n
OK no Issues<\/p>\n
C:\\Users\\Byomkesh>telnet 117.239.23.228 80
\nConnecting To 117.239.23.228…Could not open connection to the host, on port 80: Connect failed<\/p>\n
BUT telnet 117.239.23.245 80 WORKING<\/p>\n
Looks a firewall issue. But did not work even on stopping the FW. to be checked at office.<\/p>\n
Surprised no issue when accessing email.nmlindia.org via\u00a0http:\/\/www.locabrowser.com\/ and country jp,sg, uk,ca,fr,de<\/p>\n
or using\u00a0http:\/\/network-tools.com\/default.asp?prog=httphead&host=117.239.23.228<\/p>\n
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<\/p>\n
————<\/p>\n
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.<\/p>\n
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.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
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 … Continue reading 04-12-2015<\/span>