aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Low ID due to failure to recognise DNS?  (Read 3101 times)

prometeus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Low ID due to failure to recognise DNS?
« on: July 19, 2007, 01:14:55 PM »
I'm running v2.1.3 of aMule on Mac OS X 10.4 (Tiger). I have a D-Link DSL302G modem, which is not a router...I believe. Let me know if it IS a router, please.

From reading other posts I saw that I need to forward my aMule TCP and UDP ports on my D-Link modem. I followed the instructions on portforward.com selecting my modem and choosing the eMule instructions.

I followed all the steps in there to
- get a static IP; and
- add a NAT rule entry for each of my TCP and UDP ports.
I then restarted my modem.

After restarting it seems that I can't connect to any host on the internet. I can't even ping www.yahoo.com. On the other hand, when I ping a (valid) IP address, I get responses. So I blamed the DNS entries my network settings for it. These DNS servers however are the ones that my ISP told me to use. I can even see the modem's log confirming the use of these DNS servers.

If I revert back to DHCP in the network settings I have no problems connecting to a server (such as pinging www.yahoo.com), but I obviously can't get a high ID in aMule.

What can I do? Are there public DNS servers? Is this actually a DNS server problem, or maybe something else?

Thanks for any advice!!
Logged

Nerofumo

  • Jr. Member
  • **
  • Karma: 2
  • Offline Offline
  • Posts: 59
  • Just an old sysadm & dba
Re: Low ID due to failure to recognise DNS?
« Reply #1 on: July 19, 2007, 08:23:28 PM »
it seems a dns matter.

Turn for a while to dhcp and check the ip of your dns server, then switch to static ip and set the ip of dns to the same assigned by the dhcp server even if it looks like 192.168.xxx.xxx and let me know.
Logged
Nowadays you have to think like a hero just to behave like a merely decent human being.

prometeus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Re: Low ID due to failure to recognise DNS?
« Reply #2 on: July 20, 2007, 07:06:32 PM »
Thanks for your advice. Unfortunately however, I still can not connect.
First, I turned on DHCP to check the DNS servers. They replied ok on ping (IP address and host name).
Then, I switched back to my static IP using the same DNS IP address as assigned before by the DHCP server. No reply on ping to IP address or host name.

On http://portforward.com/networking/static-Mac10.4.htm I entered the info I got from the DHCP server  (Mac OS X's System Preferences > Network > TCP/IP > Configure IPv4 : Using DHCP):
  - "Enter your computer's default gateway":     10.1.1.1 (this is the address in Mac OS X's System Preferences > Network > TCP/IP > Router)
  - "Enter your computer's current IP Address":    10.1.1.3  (this is the address in Mac OS X's System Preferences > Network > TCP/IP > IP Address)
 On that web page portforward.com recommended for "First Computer's Static IP": 10.1.1.136. I used 10.1.1.136 on http://portforward.com/english/routers/port_forwarding/Dlink/DSL-302G/eMule.htm as my 'Static IP Address'.
46620 is my aMule port for incoming TCP connections.
46720 is my aMule port for incoming UDP connections.
With this data I configured the 'Nat Rule Information' as stated on http://portforward.com/english/routers/port_forwarding/Dlink/DSL-302G/eMule.htm.

I think I have configured everything to plan but without success :(  Any other ideas ???
Logged

prometeus

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
Re: Low ID due to failure to recognise DNS?
« Reply #3 on: July 26, 2007, 05:51:19 AM »
Thought I give you guys an update on this one, in case you run into similar problems.

The culprit was the IP address I set for my computer. It was out of the range that my modem was able to assign (10.1.1.1 - 10.1.1.10). From my option of 10.1.1.136 before I changed it to 10.1.1.4, and now everything works fine. Obviously, the NAT rules had to be reconfigured. After that, everything was good :)

You can see that range for a D-Link if you go into LAN > DHCP Mode.
Logged