Hi,
I have an MTNL Triband connection (DSL 590 NU) with a D-Link 502T ADSL Router.
I want to host a web server on my PC. I am using Apache as the web server software.
The index page loads without any problem with the loopback address(127.0.0 1) and the local address assigned by the router(192.168.1.2).
But when I try to access the index page with the actual IP address (59.176.x x) it shows up the Router's configuration page but not the index page.
I have also tried doing the Port Forwarding or setting up a Virtual Server for port no. 80 but still it doesn't works.
The router uses DHCP for assigning IP addresses and theseare the ATM settings:
PVC - Pvc0
VPI - 0
VCI - 32
Virtual Circuit - Enabled
WAN Setting - PPPoE/PPPoA
Any help or clues ?
Regards,
Antriksh
On Wed, 2006-05-03 at 20:16 +0530, Antriksh Bajaj wrote:
But when I try to access the index page with the actual IP address (59.176.x x) it shows up the Router's configuration page but not the index page.
Very bad practice - unless you want any Tom, Dick or Jane on the Internet to be able to configure your router without your knowing. Strongly suggest turn off http and telnet access to the router on the WAN port and *change* the administrator's password.
I have also tried doing the Port Forwarding or setting up a Virtual Server for port no. 80 but still it doesn't works.
Hmmm. DMZ and Virtual server work fine on my unit. I have got a VoIP box (in my LAN) defined as a Virtual server (port 5060) and I am able to receive inbound calls. Keep in mind, you need to define the web server IP# as a LAN client and then use that definition on the Virtual Server page (start port 80 end port 80 TCP).
Alternately, set up the web host IP# as DMZ and your box should be visible on the Internet. The downside - all other services running on this box will also be visible. Use this option only if you have "hardened" the default install.
-- Arun Khan (knura at yahoo dot com) The Official MBA Handbook on business cards: Avoid overly pretentious job titles such as "Lord of the Realm, Defender of the Faith, Emperor of India" or "Director of Corporate Planning."
On Thursday 04 May 2006 14:23, Arun K. Khan wrote:
Hmmm. DMZ and Virtual server work fine on my unit. I have got a VoIP box (in my LAN) defined as a Virtual server (port 5060) and I am able to receive inbound calls. Keep in mind, you need to define the web server IP# as a LAN client and then use that definition on the Virtual Server page (start port 80 end port 80 TCP).
Dude, he has the router configuration webserver running on port 80 and hes running the /real/ webserver behind it. So all the requests are being intercepted by the router's webserver when they should've been forwarded to the internal webserver i.e. his PC.
Hi,
Okkk...finally got the web server working. I am now running the router in Bridged mode by using a dialer and it's working. Thanks for all your suggestions.
Regards, Antriksh
On Friday 05 May 2006 00:19, Antriksh Bajaj wrote:
Okkk...finally got the web server working. I am now running the router in Bridged mode by using a dialer and it's working. Thanks for all your suggestions.
Do you really need to use a dialer in Bridged mode?
On Thu, 2006-05-04 at 21:36 +0530, Dinesh Joshi wrote:
On Thursday 04 May 2006 14:23, Arun K. Khan wrote:
Hmmm. DMZ and Virtual server work fine on my unit. I have got a VoIP box (in my LAN) defined as a Virtual server (port 5060) and I am able to receive inbound calls. Keep in mind, you need to define the web server IP# as a LAN client and then use that definition on the Virtual Server page (start port 80 end port 80 TCP).
Dude, he has the router configuration webserver running on port 80 and hes running the /real/ webserver behind it. So all the requests are being intercepted by the router's webserver when they should've been forwarded to the internal webserver i.e. his PC.
I understood what the OP was saying. I was trying to suggest alternatives with examples of what worked for me (VoIP virtual server, DMZ) but ... read on.
I have changed the subject line to reflect config problems with DLink that I encountered while trying to do some setup of my own. My modem has FW v2.0 from May/2005.
Problems: 1. Save and Reboot does not reboot the modem when invoked from Firefox 1.5.0.2 (or earlier versions) or Konqueror but does so when invoked from IE on WinXP :( 2. Even though, remote Web and Telnet management over Wan port is _disabled_ port 23 and 80 appear *open* on the WAN side and I was able to login on both ports! Fortunately, I have a non default password for the box. 3. After tinkering (Virtual server, Filter Rules) with port forwarding for a webserver, my Virtual Server Rule for VoIP (5060) appears closed on the WAN port even though it is listed active in the Virtual Server rule set.
The box was working OK until I activated the "Web Server" Virtual server rule to a LAN IP. I also changed the "admin" webserver to port 8080 but that did not help either. IMO, I don't think the DLink QA team tested some of the basic functionalities and their interaction. Will see if their tech support is of any help otherwise it is time to hit the reset button at the back of the unit :((
-- Arun Khan (knura at yahoo dot com) Children are natural mimic who act like their parents despite every effort to teach them good manners.
On Friday 05 May 2006 00:55, Arun K. Khan wrote:
The box was working OK until I activated the "Web Server" Virtual server rule to a LAN IP. I also changed the "admin" webserver to port 8080 but that did not help either. IMO, I don't think the DLink QA team tested some of the basic functionalities and their interaction. Will see if their tech support is of any help otherwise it is time to hit the reset button at the back of the unit :((
Hmm...seems to be screwed up firmware. What was the original reason for you to upgrade the firmware? IIRC there was some vulnerability in the original firmware but that could be exploited only if your router's configuration page was exposed to the internet.
Hmm...seems to be screwed up firmware. What was the original reason for You to upgrade the firmware? IIRC there was some vulnerability in the Original firmware but that could be exploited only if your router's Configuration page was exposed to the Internet.
I had once tried upgrading the firmware but even that is not so simple in 502T's case, it messed up the router and it had to be replaced....thankfully the MTNL guys did so within a day. Now that's one more point in MTNL Triband's favour , atleast their CC has improved a lot.
Regards, Antriksh
On Friday 05 May 2006 01:57, Antriksh Bajaj wrote:
I had once tried upgrading the firmware but even that is not so simple in 502T's case, it messed up the router and it had to be replaced....thankfully the MTNL guys did so within a day. Now that's one more point in MTNL Triband's favour , atleast their CC has improved a lot.
What do you mean by within 1 day? Is it within 24hours? Or on the same day? Or within 1 working day?
This is amazing :) Never thought MTNL would do such a thing.
What do you mean by within 1 day? Is it within 24hours? Or on the same Day? Or within 1 working day?
This is amazing :) Never thought MTNL would do such a thing.
The router stopped working in morning , I then lodged a complaint at 1504... ...within 3 or 4 hrs there was a call from the SDE Broadband at the local exchange enquiring about the router....I explained the problem.....then a person came to check the router when it seemed difficult to repair he installed a new one.... on the same day. Peace.
Regards, Antriksh
On Fri, 2006-05-05 at 01:17 +0530, Dinesh Joshi wrote:
Hmm...seems to be screwed up firmware. What was the original reason for you to upgrade the firmware? IIRC there was some vulnerability in the original firmware but that could be exploited only if your router's configuration page was exposed to the internet.
V1.0 firmware Web administration did not display well on Firefox at all. Figure this one out - after some interaction with the box's webserver and Firefox, the performance would deteriorate to the point the thru put was worse than a POTS dial up connection.
V2.0 is an improvement in that respect but still buggy. It has a lot more features but who knows if they work at all when a basic rule like "Web Server" Virtual Server does not port forward to the defined IP# on the LAN and opens up the admin page on the WAN port leaving uninitiated users vulnerable?
I had even written a personal letter about 502t's QA to Mr. Naik, MD DLink India (after a few frustrating sessions with their Tech. Support in Malad) but guess what - never heard back from him let alone an acknowledgement.
On Friday 05 May 2006 04:00, Arun K. Khan wrote: *snip*
V2.0 is an improvement in that respect but still buggy. It has a lot more features but who knows if they work at all when a basic rule like "Web Server" Virtual Server does not port forward to the defined IP# on the LAN and opens up the admin page on the WAN port leaving uninitiated users vulnerable?
What about the CLI? Can we use that to configure the router?
I had even written a personal letter about 502t's QA to Mr. Naik, MD DLink India (after a few frustrating sessions with their Tech. Support in Malad) but guess what - never heard back from him let alone an acknowledgement.
Dont keep too many hopes from these guys. But maybe if enough users pester him then they might do something about it...
On Wednesday 03 May 2006 14:46, Antriksh Bajaj wrote:
Any help or clues ?
You wont be able to reach your actual webserver because the requests on your external interface ( 59.x.x.x ) are being served by your router's webserver as its running on port 80. There are two options in this case I guess: 1. Setup a DMZ 2. Somehow change your router's configuration webserver's port from 80 to something else and then forward port 80.
-
Antriksh Bajaj -
Arun K. Khan -
Dinesh Joshi