@terminills:

Thanks for the addition. Yes, you are of course correct , it completely depends on the router (or configuration).

To give an(other) example: i am able to use (and have) virtualized ports on my router that can be configured explicitly, so if i connect my AROS machine to one of those ports, i am screwed as other rules apply (as they are configured for completely different machines/circumstances).


Anyhows, the point that i wanted to get across is that as long as you are able to ping your loopback (127.0.01) and your assigned ip address (whatever ip-address it was assigned), then things are more or less out of AROS' hands and have more to do with the setup of your network/router (and of course AROS settings do have to match those, but that should be a matter of correct configuration).

How that configuration for AROS should look like depends on each individual situation and can be checked more or less with the ping results). For instance it would be nice to know if at least the internal network was configured correctly (e.g. local machines are reachable by ping).

Quote:

Never assume the address range is in the 192.168.0.x range. It depends on the manufacturer. Buffalo uses 192.168.2.x, asus uses 192.168.1.x. And those are just the models I've personally used it may even vary based on models.

If you are going to manually setup an IP address you should always verify with the router settings.

Next step would be pinging your own assigned ip address (usually in the range 192.168.0.x) which is assigned by your dhcp server.

After that, check which other machines are pingable in your network, e.g. router/gateway and other machines/devices.

Also check if you can ping this (troublesome) machine from another machines in your network.

Are you able to reach any other machine on your own network with pinging or is it only the outgoing ip addresses that causes problems for you ?

The latter could hint on a wrongly configured router/gateway or perhaps even a blocking netmask. It's hard to tell things about a network infrastructure that you're not familiar with.

I pinged the 127.0.0.1 with no errors

Ping saying no route to host is problematic.

sorry in advance but i have to ask. Are you sure your nic is listed as working and correctly setup with the correct driver and all ?

please note that sometimes it can seem to last forever for the network to pick up for aros. It's not uncommon to have to wait 1-2 minutes for the network to come up. Also make sure when selecting drivers for your nic to do a reboot (it shouldn't be necessary, but just to make sure).

Also be aware that only one nic can be active at the same time.

Would you be able to open a shell and type "ifconfig -a" (+ enter of course) and paste its output here ? (a screenshot is ok as well)

ps: alternatively check ping 127.0.0.1. If that fails as well, you can be sure your nic isn't active at all.

Ping says no rout to host

I achieved a automatic IP address ,Gateway,primary DNS and secondary DNS . The hOst Name is Arosbox and Domain /work group is the same

Hi retrodave,

resolve host name errors seems to indicate problems with dns. Since you are wired, are you behind a router ?

If so, try using dhcp and see if your router is able to 'fix' things for you.

In case you _have_ to use static ip addresses for your network then make sure you point dns to your isp dns server or alternatively use opendns (as described in the manual chapter 3.4).

Are you able to ping static ip addresses without problems ? (open a shell and type "ping xxx.xxx.xxx.xxx" and replace xxx.xxx.xxx.xxx with a valid (working) ip-address.

I keep getting could resolve hoist name error when trying to connect to a website via OWB browser. Settings are set correctly unless I am missing something .Help ,Ideas ?

In fact, there is currently no working AROS driver for Intel gigabit NICs. IMHO it's a failing of the HCL that it includes hypothetical drivers such as e1000e.device.