Diffs installing AmiTCP3.0b2

[patrik]

Make sure you havent named the interface "3c589", as the last number in the interface name is used for deciding which unit-number to open of the specified device.

From the documentation in top of the interfaces file:

Code: [Select]

# The new-style network interface name consists of interface device name
# concatenated with interface unit number, ie. if the interface name is
# "slip0", then the interface device name is "slip" and the interface unit
# is 0.  The network interface name should not contain digits ('0' ... '9').
/Patrik

[patrik]

@dvvrue95:

Your netdb-myhost file is a bit wrong.

It seems you have supplied a load of search-domains in the form of ip-numbers, which is wrong. Search-domains works so that if you try to access the host 'testtest', it will amongst other things try to combine that with the search-domains you have specified.

Say for example that you have host.com specified as a search-domain and then try to ping testtest, it will amongst other things try to ping testtest.host.com. Adding several search-domains will usually slow down the hostname resolving btw.

Also, no nameserver specified (maybe you didn't enter one when asked during the installation?), which you do with the keyword 'NAMESERVER', just like you specify search-domains with the keyword 'DOMAIN'.

So remove those search-domains which are ip-numbers only keeping your default 'host.com' and add a nameserver you know is working on your local network. After that AmiTCP should be able to resolv hostnames.

I can't see why you are having troubles with your paths, but if I were you I would take a backup of your S:User-Startup and create a new empty one and start adding sections to it from your backup one by one and see when you start gettings troubles with your paths.

Btw, why do you start the MagicWB-demon both in your Startup-Sequence and your User-Startup?


/Patrik

[patrik]

@dvvrue95:

I assume you have some sort of pc on your local network. Your best bet would be to use the same nameserver(s) as that one.

If you are running Windows, in a command-prompt run "ipconfig /all" to amongst other things see which nameserver(s) are used.

If you are running a Unix derivate OS, you will in most cases see which nameserver(s) are used if you in a shell run "cat /etc/resolv.conf".


/Patrik

[patrik]

The router most likely only put devices using DHCP in the active list, as it is the one who has assigned their adresses.

As you can ping your pc it sounds like your router is acting wierd with non DHCP devices. Make sure don't have to set some option to allow it to forward traffic for non DHCP devices. Try and see what happens if you use static addresses on another machine on your network.

Also, from the Amiga, can you ping:
- the ip of the router?
- the ip of www.google.com - 66.249.93.99?
- www.google.com?

The reason you get the hostname twice might very well be the work of the router - as it is your pcs dns, it might apart from forwarding normal queries, very well resolv hostnames for ip-numbers on your local net and when it doesn't know a hostname it just supplies the ip-address as hostname - thus you see the ip-number twice. You could always post the output here.


/Patrik

[patrik]

Amiga Explorer unfortunately does'nt work with AmiTCP 3.0b2 as it uses asynchronous sockets in a way which requires AmiTCP 4.0 or greater.

Send them a mail and ask them to apply support for 3.0b2 .

If not, give smbfs a go. Just search the forum and you will find advice of how to use it.


/Patrik