[iyonix-support] Re: Resolver not working
- From: rickman@xxxxxxxxxxxxx
- To: iyonix-support@xxxxxxxxxxxxx
- Date: Wed, 03 Feb 2010 11:43:31 +0100
<4B68A88C.8050807@xxxxxxxxxx> Peter Naulls wrote:
> On 02 Feb, <rickman@xxxxxxxxxxxxx> wrote:
>> I think that Resolver is not working on my Iyonix 5.16.
> ...
> The first question is if you have proper connectivity,
> and indeed ping to an IP address would be a start,
> but might not be everything (it is ICMP, not UDP
> for starters). Also look at the status of *ekinfo.
*ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0 ms
*ekinfo
EtherK device driver for Intel PRO/1000 network controllers, vers 0.21
DCI Version 4.05
Supported network cards detected: 1
Unit 0 (location: Motherboard)
Ethernet address 00:09:95:00:15:C8
Link is up; 100 Mbps Full Duplex
Controller mode: Multicast, reject frames with errors
Frame types claimed:
Ethernet 0800 (multicast) handler=(FC2EC5AC,FB40743C)
Ethernet 0806 (normal) handler=(FC2EC5AC,FB40743C)
Ethernet 8035 (normal) handler=(FC2EC5AC,FB40743C)
Hardware statistics summary:
TX frames 23 : RX frames 2
TX bytes 1,826 : RX bytes 158
TX errors 0 : RX errors 0
> Beyond that, if you can try and repeat the resolution
> using ping to a name address (e.g, google.com) and
> see if you get the failure. If you can cause it
> to repeat somehow, then you might have a clue
> about what is going on.
Here is the result of pinging gmail.com by name and by numeric
address:-
*ping www.gmail.com
ping: unknown host www.gmail.com
*ping 74.125.79.109
PING 74.125.79.109 (74.125.79.109): 56 data bytes
64 bytes from 74.125.79.109: icmp_seq=0 ttl=244 time=50 ms
64 bytes from 74.125.79.109: icmp_seq=1 ttl=244 time=40 ms
John
--
Midland User Group - http://mug.riscos.org
No sé nada, y no estoy incluso seguro de ése.
---
To alter your preferences or leave the group,
visit //www.freelists.org/list/iyonix-support
Other info via //www.freelists.org/webpage/iyonix-support
Other related posts: