Printable View
Hi all
right. i found out waht the problem was pertaining the widows server queries forwrding problem. it is to do with the router.
Problem si that using th estatic ip assigned by my ISP, i need to sue this for all web quesries and makeing the server public. problem is that no queries are being forwrded using the public ip address via the router.
Any dies or where i cna get detialed info on how to solve this??
ta
Kai
http://www.portforward.com/english/r...I-604index.htm
Pick the software, or just pick any program, and you'll see where to forward ports on the 604. D-Link calls it Virtual Servers. (Make sure you assign that computer an address outside the router's DHCP range.)
You might also want to take a look at www.no-ip.com. It'll give you a named address people can use, rather than having to remember a numeric address. (And you can use it with a dynamic address from your provider, so you don't have to pay for a static address.)
You could always shove it in a DMZ for testing....
It doesn't sound like he's having port issues. It sounds like he's saying his system isn't using the public IP address... which doesn't make sense.
I'd suggest hiring someone to come out to your house to setup your network.
I'd also like to add that I've setup a lot of D-Link routers and they all seem to work... like crap, lol. I try to stick with business grade Netgear routers.
some routers like mine have a browser based interface.i.e it has a mini webserver running
few days back when i installed apache,it was running fine if i typed http://localhost but din work if i typed in my external ip address...instead the routers interface was popping up
localhost goes to 127.0.0.1 which is your own PC. If you don't have a server installed onto your PC, than localhost shouldn't go to anything (definately not to a router). Showing the browser interface via the external IP address is also not a good idea as that's a security risk cause anyone can manage your router.Quote:
Originally Posted by litlewiki
You should, instead, go to the router's internal ip address (usually something like 192.168.1.1 or 192.168.0.1)
If you have a router and are running a web server you should enable HTTP requests on your router and forward port 80 (and any other ports your web server(s) is/are listening on) to your server's internal IP.
External requests to his public address aren't getting to his internal server - that sounds like a port forwarding issue to me. And, IIRC, D-Link is one of those companies that got it right - it won't forward to a leased (internal) address.Quote:
Originally Posted by kasracer
If you wouldn't have taken my quote out of context you would have realized that, to me, it sounds like he's saying queries arn't even making it to his router via the public address (which sounds really odd). Something like that would not be a port issue.Quote:
Originally Posted by Al42
That's not saying it couldn't be a port issue; I'm just not sure what he's asking for.
What are you talking about? The last D-Link router I owned let me forward to any address, including leased addresses.Quote:
Originally Posted by Al42
If the router didn't, I wouldn't call that "right" at all as there are many cases when you need to forward ports to a computer that has a leased address. All routers allow you to do this even high end Cisco equipment.
I wouldn't begin prasing D-Link, especially after their GPL violations and having their customers bombard an NTP server they didn't own and hard coded it into the Firmware of hundreds of their products.
Hi,
right after taking all thsi onboard, and using port forwarding and all the other little trinkets that cvarious sites offer.
none of thsi is working.
it is stil not letting me access any sort of site through the public address.
88.one05.one74.one2one
or access any private ip address, or forward any queries from the public ip address to the private ip address, regardless of any port.
no traffic is being blocked, and NAT and firewall is enabled on the private ip address.
A little more information is given below.
on this router, there are 12 IP addressses, only one of them needs to be accessed form the internet (the above). consulted with D-link and they say that if the port forwarding rule is correct, then this should allow the queries to access the ports. but it isnt.
any other ideas??
Ta
Kai
You're attempting to connect to this computer from the internet, right? Not from behind the router you're using to forward the port?
You set the router to forward to x.x.x.x, your computer, which is set to use DHCP. Some people turn off computers set to use DHCP. You turn off the computer you're forwarding to for some reason. Someone else turns on a computer set to use DHCP. You turn on the computer you're forwarding to. The port is now forwarded to???? You? him? No one? Odds are, though, that the forwarded port is now useless.Quote:
Originally Posted by kasracer
(There are some routers that can be set to lease addresses, but the same address to the same MAC all the time. This is a static address, not a dynamic address, so it's not really leased, it just saves you having to set the computer to use a static address.)
At first it sounded like you couldn't go to any websites and then it sounded like you only want 1 computer that others can access from the internet so I'm a bit confused. If it's the former you may need to call your ISP or the router computer. If the latter then you'd need to setup port forwarding.I don't see your point in posting this. It's obvious something like this could happen (especially if the computer is turned off) but there are still situations where you might want to forward a port to a computer that's utilizing a leased address.Quote:
Originally Posted by Al42
What if you need to run a test or need someone to connect directly to you? Setup a quick port forward temporarily and you're all set.
This is getting off track anyway.
Hi,
first of all , the computer is not turned off, it never gets switched off.. its a server!!1
The problem is that i am setting this server up to host websites and i can access the server from the internet. port forwrding is set up, access control is fine and ok. As for the server side, IIs is set up and configured. DNs is set up adn confgigured, and so is active directory for that matter as well.
so the problem is that I cant use the public IP issued by my ISP to access the server, i also cant use the IP adderss issued by the router (obviously).
So the problem is tht I am not able to access the server from the internet which is an issue with the router.
To round this off, i ve posted this as ive tried every possible angle I can humanly thin kof, and further more this is probably alot more that most people would try as i am very well qualified in my field indeed, but have never used a d-link router, therfore I ve posted this to ask for advice and maybe a different agle or take on this problem, not for people who dont actually read the previous posts to assertain the root of the issue in hand.
Oh and to put light on the issue about the DHCP. The DHCP for the router is turned off, and all Pc's wihtin the network are using static IP's only. hoipe this helps.
so after a recap on the problem, any ideas?
thanks
kai
Hi,
ok then. Managed to get the quesries as far as the router login screen and thats it.
Also, have found out that were ona consumer package, so another question is that do I have to have a static IP address to forwrd queries through standard TLD's? as were currently using a dynamic IP issued by the ISP.
but eventhen, how do the queries to this ip get forwarded to the router?
This is really baffling me adn doing my nut in now as there is physically nothing wrong with the system at all, the router is simply not forwrding the queries relevant to the rules createe in the port forwarding section!!!
HELP!!!
kai
Sounds like a port forwarding issue from what you're describing here. I've setup servers before and it's usually as simple as forwarding the needed ports and you're done.Quote:
Originally Posted by kaihirst
I set this up with a D-Link router, actually.
This doesn't make sense. What queries? Just trying to access the computer via a web address? If so, again, usually that ability to modify your router is turned off by default and I'd recommend that. Secondly, it sounds like port forwarding is not properly setup.Quote:
Originally Posted by kaihirst
It's best to have a static address otherwise you'll have to change your IP with your nameserver to forward your domain name to it everytime it changes (however, if it never gets turned off it most likely won't change much (with my ISP it never changes, it's virtually static as I've had the same IP for almost 2 years now)). However, dynamic should still work.Quote:
Originally Posted by kaihirst
Like mentioned before, it sounds like port forwarding is not properly setup on your router and I'd recommend getting a professional to configure your network. That and/or maybe look at getting a business/professional grade router rather than a consumer D-Link product as I've heard of issues with D-Links restarting when their hit with too much traffic.
Hi,
right
ive established that you dont need a static ip but it helps. Fact is that the server never gets switched off so the IP will likely never change at all, but if it does, ive got this covered anyhow.
it is a port forwrading issue and the router is configured incorrectly (possibly) but I cant see where. NAT and Firewall are enabled, DMZ is set and allowed for the internal IP address, ICMP and Ping Aloowed and enabled, port forwarding is set for the correct ports that are running for IIS, yet still public computers are not able to view or connect to this server, and computers that are members of the domain are sent directly to the router login!!!
What the hell is going on with this..
Ta
kai
That doesn't make sense. Call D-Link support or have a professional setup your router because something is not right and it's hard to tell what. DMZ should basically make the server accessable to anyone on any port on the internet.
You can't forward ports to a computer in the DMZ - choose port forwarding or DMZ, not both. (Some routers ignore port forwarding if the destination IP is in the DMZ - most don't.)
"computers that are members of the domain are sent directly to the router login" When connecting to which address? 192.168.0.1? The server's internal address? The external address?
"how do the queries to this ip get forwarded to the router?" No forwarding at that point in the process - the router's IP address is the one your ISP gives you, so the requests go to the router. It's how they get from the router to your server that's the problem here.
BTW, just in case the server should go down and you get a different IP address, you should look at www.no-ip.com.
Do you have the Windows firewall on the server enabled? (It's enabled by default in XP.) If so, you have to punch a hole in that too - or just turn it off, since the D-Link is a firewall.
Tests:
From a computer in the domain, connect to the internal address of the server with IE. Does that work? (Do you get to IIS?)
From a computer outside the domain connect to the public IP address of the router (not the 192.) with IE. What do you get? Timeout? Unable to connect? The router login?