Hai folks, *My computer is a computer of a 500 computers network within our company. * i have been given a STATIC local intranet ip 192.168.10.168 assigned by our IT department via their router. * i have the internet facility provided through the above mentioned intranet for which i get a dynamic ip ex: 188.54.208.205, 176.44.107.21 * i have installed WAMP server. my current project for the company i am doing should be able to access via internet in addition to the local access. local access is the primary access method. so now i have installed a free dns service like dyndns. at the setup of that, i have choosen a free subdomain ex: my.freedns.com they offer. then i assigned the ip ex:188.54.208.205. also installed their desktop client for monitoring ip changes auto updates. Now the problem is : when i hit my.freedns.com the page displaying is of our internet service provider. not of my project homepage . How can i fix so when i issue above subdomain it will show my webserver default page?
1st thing I would do is contact your ISP to find out if you have to upgrade your service to allow having web servers behind your router. You can also see if you dynamic DNS provider does port forwarding from 80 to per say 8080 and have your webserver listen on 8080.
Honestly, it sounds like a bad idea, unless the webserver is in a DMZ? It's coming across like it's on a desktop as part of the LAN. Just don't do it, if you're wanting to allow external access. I doubt your network admin wants to allow port 80 traffic to a PC on the LAN. I wouldn't even allow it through to 8080. Why do you want to allow external access? Is it really needed? Is the WAMP installation just for a development server and not live?
@ryan_uk all the intricacies make the whole situation hard to understand. I would think that if he can install WAMP (along with other software) on his desktop and he was given a project that "should be able to access via internet" that there is some sort of oversight and the network team wont let his system be a wide open gateway into their LAN from the internet. However, I could be wrong.
Whatever the OP has in mind is heading for disaster, wanting to leave a LAN PC so exposed. Hint to the OP - get a dedicated server hosted at a datacentre. No risk to your internal LAN then.
So the OP needs to clarify the situation, because what tipped me off that this is a legit setup is that the network team provided him with a static local IP (as opposed to dhcp) and he is using server software. OP mentions desktop in there, but only related to the dynamic DNS software. I know assuming is bad, but if OP can get public traffic to his server than he must have more going on than just plugging a PC into the DMZ. OP, please clarify your operating environment.
There's a world of difference between approving a static IP and allowing certain incoming ports, especially as this is a commercial environment (a LAN). Furthermore, the static IP provided is a private one, so port forwarding comes into play. The issue is the OP doesn't have public traffic to his PC: The OP wants traffic routed to a PC on the LAN, rather than a server on a DMZ. I can't imagine any (sane) network admin allowing this scenario, due to the security issue it creates. The OP needs to find out if his network has a DMZ (or one can be set up - strongly recommended, it will give you extra security) to place a webserver on. So, the OP needs ports forwarding from the external dynamic IP to his internal network (private IP) and leave a nice gaping hole for hackers to try to exploit. That will require portforwarding set up on the network's router (the "internet facility"). If the ISP is currently capturing port 80 requests, that's just another issue that needs resolving (if they will even agree to it).
You make perfect sense, but the OP never said he wanted the connection to a PC. It just sound extremely likely that it is a PC because he says "my computer". I don't want to debate whether or not it's a PC or server because I think it's a PC too. The 500 computers on that LAN could all be servers in a lab, but we wont know until the OP explains the situation.
OK, I'll rephrase: an electronic device for storing and processing data. Rather than using PC for short.
oic, your saying it's dangerous for any system in general to have both LAN and WAN interfaces unless in a dedicated DMZ. I agree with that. I also feel that doing this with a windows system (may not have a choice) and having the database on the web server are also bad ideas as well. I would even go so far as to manage the system out of band and if they want a system ridding on the WAN and LAN split them up and mirror the LAN to the WAN so that traffic is one way so and is always going out and never in. I would also plop a proxy in front of the WAN web server just for an added level of security. The proxy built bare minimum (no ssh, no ftp, etc.) and setup to reject everything outside port 80.
Yes mate, that's all I meant, network segregation for security's sake. And I agree with you, Windows is a bad idea as a server. Well, a server is only as secure as the admin makes it, but that's where Linux is far superior. I am sure my mate who works for M$ will disagree with me and we'll have a raging argu.. er, debate.
does your ISP allow you to use port 80? sounds like they have it blocked outgoing. You may want to try another port, maybe 8080, or 8888.