I have set up EndianFW 2.2RC3 with the workgroup name "sagesse". Endian is
the DHCP server and the problem I am having is that machines on my network
are resolving to external addresses rather than internal addresses. For
example, there is a Windows machine named "Caspian" that Endian has given
the IP address 192.168.0.194. When I ping Caspian from a command prompt (for
example, from an Endian SSH shell), I get the following:
[EMAIL PROTECTED]:~ # ping caspian
PING caspian.sagesse (8.15.7.107) 56(84) bytes of data.
64 bytes from 8.15.7.107: icmp_seq=1 ttl=49 time=80.3 ms
64 bytes from 8.15.7.107: icmp_seq=3 ttl=49 time=82.2 ms
64 bytes from 8.15.7.107: icmp_seq=4 ttl=49 time=92.5 ms
--- caspian.sagesse ping statistics ---
5 packets transmitted, 3 received, 40% packet loss, time 4009ms
rtt min/avg/max/mdev = 80.364/85.053/92.530/5.348 ms, pipe 2
Does anyone know why Caspian would resolve to 8.15.7.107 and how can I
correct it so that it resolves to the proper internal address?
Thank you,
Reg
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Efw-user mailing list
Efw-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/efw-user
