Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Hodgkinson on August 24, 2008, 11:31:19 AM
-
Hi,
So far when I've been using AmiTCP I've found (By guesswork) that for a network connection to work I've have to enter the IP address and network name of the target machine into the AmiTCP:db/hosts file beforehand.
Is there any way for AmiTCP to gain the IP address of the target machine automatically; in order to allow it to work with dynamic IP addresses without having to manually edit the hosts file each time the target machine is rebooted?
Thanks,
Hodgkinson.
-
Err. Make the target box use dynamic DNS, such as http://www.dyndns.org ?
(This has absolutely nothing to do with AmiTCP though)
-
If this happens within your own network, you need to set up either
- a DHCP aware DNS server
- reserved DHCP addresses for the MACs of your required hosts (enables central management of the addresses)
- simply use static IPs on the hosts in question
-
Hmmm. Suppose I can't make any alterations on the target host (E.g., say it's a shared folder on a University network, per chance...). Assuming everything’s set-up as it would normally be configured for the average network, what would I have to do to connect to the shared folder?
I guess that I wouldn't have to bother poking around in the hosts file anymore, as the DNS server at their end would resolve the host name?
Since my main PC has a static IP (We found that stuff generally works better when all the IP's are tied down on the home network...), then I guess for when I've just got the PC plugged straight into the Amiga and disconnected from the rest of the Uni network, then would it still be a requirement for the IP/name of the PC to be in the hosts file?
(Btw, the ins and outs of networking isn't one of my strong points...)
Hodgkinson.
-
If the University's DNS server has an entry for that host, and the DNS server is available from outside (i.e. it replicates its entries to public DNS servers) then accessing it should be no different to accessing any other DNS name, such as a web site. If the DNS server does not replicate its entries and you are unable to resolve the name through DNS, then you will have to either use the IP address or set up a hosts file to manually resolve it. In both cases, if the IP address of the remote machine changes, you will have to change the IP address you are using. A DNS server would usually take care of this for you, but of course that doesn't help if the DNS server only works within the University network.
--
moto
-
Thanks for the tips, folks.
From what I read of the University accommodation, each room is outfitted with a 10Mbit (Sigh, can't complain really) network connection which appears to be intended for internet access, so buy the looks of it I'll be wired straight into some sub-section of the Uni network.
The general idea im working along is "Wouldn't it be great if both my PC and my miggy could access internal shared folders on the network". In particular, if I could access my network profile from my miggy across the network, dumping downloaded files from Aminet and other such places onto the miggy becomes a whole lot easier...
So...
If I could obtain the DNS server IP(s), I'd enter these into AmiTCP and let AmiTCP handle the host names (Just remembered the dialog boxes in the installer)? Anyone any idea which file they should be entered into (Since it's already installed)?
Can user profiles be accessed in the same manner as shared folders, providing the correct credentials are provided and the location of the profile folder is known? (Just guessing here)
Heh, and im not even there yet...Nothing like planning ahead…
Hodgkinson. :crazy:
-
Is this along the right lines?
-
Well, the oldskool solution is to build a LAN with fixed IP addresses for sharing between the computers. One of the machines (the PC in this case I suppose) would then connect to the 10mbit and share the connection for the LAN, preferably by using NAT (to allow inbound connections for the other boxes, say for IRC, FTP etc).