AmiTCP Help Needed

[edd_jedi]

I recently moved house and am trying to get the internet working on my Amiga 4000 in the new house. As the new routers IP address is the same (192.168.0.1) I assumed it would just work, but sadly not. I can ping the router, but no websites.

I am using AmiTCP on ClassicWB 3.1 with an Ariadne II Ethernet card. I set AmiTCP up about 5 years ago so cannot remember the process too well, but it was working in the old house and I remember that I followed this guide:

http://megaburken.net/~patrik/AmiTCP_Install/

As far as the Amiga should be concerned nothing has changed, so I don't know why it's not working. I transferred my Virgin Media account to the new house and got a new router from them, but the IP address of both is the same (192.168.0.1) so I don't see what else I would need to change. I have tried a few different random host IP addresses, but no difference.

My settings are in the attached screenshots, the guide above says in the troubleshooting section that being able to ping the router but not websites indicates a nameserver issue, but as you can see they match in the two screenshots attached.

Any help appreciated!

[coldacid]

I would suggest verifying the DNS configuration on the new router. Have you also tried pinging a known-good IP address outside of your local network? If you can't get a ping response from 8.8.8.8 for example, then DNS is probably not the problem.

This kind of thing is why I have my own router running OpenWRT for running my network, and just putting whatever ISP-supplied networking equipment into bridge mode to connect between my router and outside the home. It greatly simplifies troubleshooting, so long as you have the networking know-how.

[edd_jedi]

Thanks for the suggestion, I can ping 8.8.8.8 but still can't get any domains to load or ping, so what does that mean?

[mark_k]

You could try changing NAMESERVER from 192.168.0.1 to 8.8.8.8 (that's Google's public DNS).

[edd_jedi]

Originally Posted by mark_k

You could try changing NAMESERVER from 192.168.0.1 to 8.8.8.8 (that's Google's public DNS).

Thanks, but that didn't work I'm afraid. Unfortunately I don't know much about networking, but I just logged into the new routers control panel and noticed DHCP is turned on with the 'starting local address' of 192.168.0.10. I tried changing the nameserver in AmiTCP to that as well, but still no joy.

I assume it must be something on the new router I need to change to match the old one, any idea what? Unfortunately I don't have it as Virgin took it away.

[jayminer]

Since you said you can ping 8.8.8.8 then it seems the networking is working except for name resolutions. If you check on another computer that is connected using DHCP - what does it say it's DNS is? If you are using windows you can check the current DNS settings by opening a Command Prompt and typing "ipconfig /all" and look for the DNS server line. If that says something else than what you've already tried - then try that.

[coldacid]

Yeah, definitely check what the nameservers are set to on a computer on your network that is able to resolve domain names. 'Starting local address' for DHCP means that IP addresses assigned to devices in your network will start at 192.168.0.10, it is going to be just another device on your network and not necessarily one that runs a DNS daemon.

Can you at least connect to 8.8.8.8 port 53 from another computer on your network? If not, you might need to ensure that outgoing traffic to port 53 on computers outside your network isn't firewalled off. It shouldn't be, but I never trust ISPs to let you use DNS resolvers that aren't theirs without having to jump through some hoops first.

[edd_jedi]

Thanks all, that was it. Checked the DNS address on Windows and it was different, so I changed it to that in the db/netdb-myhost script, and I can now ping host names and browse websites again

[coldacid]