Topic: How to setup a D-Link Modem/Router?

[Smitro]

Hi all,

Not sure if this is the best place to post this... (you know the usual disclaimer)

I can't see my sites (domain names) from inside the network.

I'm using a D-Link DSL-502T Modem/Router to handle the routing. I've port forwarded everything I need to my server. From the outside all websites and  other services (eg. mail, ssh etc) are working.

From the inside of my network all requests seem to get stuck at the router (it doesn't seem to port forward on the inside). I can ping but I presume I'm just pinging the router.

If I use the proxy server on the server it will work, but I don't want to do that, I prefer a straight through connection to the internet.

I can access the server using the internal ip address or host name, but this is no good for my virtual hosts.

I had all this working on my Gigabyte Router, but have had to change my configuration around a little and now I'm using my D-Link modem/router to handle my IP address.

Does anyone have the D-Link model above or similar that might be able to share with me how they have it setup.

[Smitro]

To answer my own question... I think this is going to be not possible.

From D-Link's web site:

Please note that from inside your LAN you will not be able to access your server using its public IP address or name. On your LAN you will need to use its local IP address instead (10.1.1.3).

http://faq.dlink.com.au/supportfaq/DisplayTemplate.aspx?TemplateId=24077

[p-jones]

Is it really an issue ??

Why not just access your servers by Netbios name fom within your network ? //serevrname or //servername/music or whatever

[Smitro]

I'm building php web sites, so they need to be processed by the web server. I know it's possible to go to http://servername/ibay_name/ but that's not very good because I like to be able to send direct links to people, and I can't look them up my self first to copy and paste.

I thought this problem was fixed if I passed everything through the proxy, but it turns out that only the main domain works, the virtual ones dont.

[d6hq]

You can set up an internal DNS server that points your virtual domains at the correct internal IP address OR if it is just one PC that needs to work correctly edit the HOSTS file on that PC as follows

www.mydomain.com              192.168.X.X

The Pc will then look locally for the virtual domain

[Smitro]

I was thinking about changing my PC's host file, but there is a couple of machines on the network. How hard is it to setup and internal DNS? Is there any how to's? (I'll start looking)

[CharlieBrady]

You can set up an internal DNS server that points your virtual domains at the correct internal IP address ...

One already exists - the SME server. Use the SME server as the router rather than the D-Link. Configure clients using DHCP, and everything "just works".

[Smitro]

for testing purposes, I just changed my IP address to static and DNS and Gateway to point to my server. I still can't browse to my Virtual domain names, but I can browse to external web sites. Would it be possible that the DNS is disabled on the server? (interesting that external websites work though). The server is running in "Server-Only" mode if that changes anything?

Let me know if you need any more info from me.

[Smitro]

If this helps... I can get to the primary domain that is configured on the server. Infact this is what happens when I do a tracert.

Code: [Select]


Tracing route to mailoz.com [192.168.1.254]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  box1.mailoz.com [192.168.1.254]

Trace complete.


But when I do the same to one of my virtual domains that is on the same box.

Code: [Select]


Tracing route to digitalsnapper.net [202.63.41.67]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  box1.mailoz.com [192.168.1.254]
  2    <1 ms    <1 ms    <1 ms  pc-00002.mailoz.com [192.168.1.2]
  3     1 ms     1 ms  cust0323.qld01.dataco.com.au [202.63.41.67]  reports: Des
tination protocol unreachable.

Trace complete.
pc-00002.mailoz.com [192.168.1.2] is my router.

[wjhobbs]

Smitro,

This is the setup I use to address this problem. Don't know if it will help.

My virtual domains are all set to resolve locally.

I have my SME Server specified as the primary DNS server on my internal workstations. (In my case this happens because the machines use the server as their DHCP server.)

In that way, any references from internal machines to my virtual domains will resolve directly to the SME server. These requests never get outside my local network.

Any references to external sites from my local machines will get resolved automatically (by SME's built-in DNS server, communicating as necessary with public DNS servers).

Traffic originating outside goes to public DNS servers and gets routed to my external IP address and then forwarded to my SME server by my modem/router.

John

[wjhobbs]

How hard is it to setup and internal DNS? Is there any how to's? (I'll start looking)

The SME Server already has an internal DNS. You manage it through the server-manager panel, using the 'Domains' menu item and then if necessary the 'Hostnames and addresses' functionality.

John

p.s. Be aware that sometimes changes to these entries take a while to get reflected in the system's DNS.

[Smitro]

I think I might be getting some where...

Under "Hostnames and addresses" I only have my primary Domain.

When I say add Host Name. In the Domain box, I can only select my primary domain.

Is this correct, or should all the others be listed?

I remember before the upgrade from 6.5 I had all my domains and host names listed in there.

[wjhobbs]

Go to "Domains" and confirm that all of your virtual domains are listed. Then for each one, ensure that it is set to "resolve locally". (The 'resolve locally' is new in 7.0)

Then you should see them listed in the "Hostnames and addresses".

John

[Smitro]

You guys are champions.. I told each domain to resolve locally, then told me router to look at my server for DNS now everything just works...

Thanks all for your help.

J.