From: Doug Troyer (dtroyer@stmartin.edu)
Date: Fri Aug 06 2004 - 16:39:02 CDT
Will do Todd. I will get the tcpdump and see what the G5 is saying if
anything.
Thanks,
Doug
Todd K. Watson wrote:
>Still, the best way to find out what is going on is to sniff the
>connection. OSX should allow you to build/run tcpdump. If you see the
>DHCPOFFER from the NetReg system on the OSX box, then you're half way
>there. Next is to look for what the OSX box responds with. If you don't
>see the OFFER on the OSX box, then you know something is firewalling it
>from making it there. If you see the OFFER followed by a REQUEST from the
>OSX box, then you know something is firewalling the returned packet. It's
>a tedious process, but usually will result in being able to narrow down
>exactly what is happening.
>
>Todd
>
>On Fri, 6 Aug 2004, dtroyer wrote:
>
>
>
>>Yes, this would be a possible solution, but, the G5's firewall is off.
>>Sorry I neglected to mention that earlier.
>>The two log entries are the registered PC/MS based computer and the
>>G5/Apple unregistered computer.
>>The two IP ranges are registered and unregistered domains.
>>
>>It seems not to matter what ever PC we plugin, it gets DHCP IP addresses
>>from Netreg.
>>This is a definite puzzle to me.
>>
>>By the way, the G5 was out of date previously with 3.2 OSX and has been
>>updated to 3.4.
>>In either case, the G5 will not accept the DHCPOFFER.
>>
>>
>>Todd K. Watson wrote:
>>
>>
>>
>>>Are you certain that you do not have another DHCP server on your 10.4.254
>>>network? The machine which you used as an example as a comparison was on
>>>a different subnet. I would try sniffing (with tcpdump, ethereal, etc) on
>>>the OS-X box to see if perhaps the system is receiving an accepting an
>>>offer from another DHCP server.
>>>
>>>Actually now that I think about it, if that was the case, you would
>>>expect to see a DHCPDECLINE in response to the offer. So, it would seem
>>>like the OSX box is not seeing the offer at all. That would indicate a
>>>host-based firewall issue perhaps on the OSX machine. Check for that.
>>>
>>>Todd
>>>--
>>> Todd K. Watson
>>> Senior Systems and Network Administrator
>>> Southwestern University, Georgetown, TX
>>> tkw@southwestern.edu || TEL:512.863.1508 || FAX:512.863.1605
>>>
>>>On Fri, 6 Aug 2004, dtroyer wrote:
>>>
>>>
>>>
>>>
>>>
>>>>We have a problem with the apple G5 computers running OSX.
>>>>It seems that the dhcp server is sending DHCPOFFER to the computer but
>>>>the G5 will not respond to the offer.
>>>>
>>>> Aug 6 13:27:36 netreg dhcpd: DHCPDISCOVER from 00:03:93:49:ab:a8
>>>>via eth0
>>>> Aug 6 13:27:36 netreg dhcpd: DHCPOFFER on 10.4.254.253 to
>>>>00:03:93:49:ab:a8 via
>>>>
>>>>This entry continues for a while for the G5.
>>>>
>>>>Normal dhcp operation works for MS Windows based computers.
>>>>
>>>> Aug 6 13:22:46 netreg dhcpd: DHCPDISCOVER from 00:03:47:e5:cb:b8
>>>>(test1) via eth0
>>>> Aug 6 13:22:46 netreg dhcpd: DHCPOFFER on 10.4.4.254 to
>>>>00:03:47:e5:cb:b8 (test1) via eth0
>>>> Aug 6 13:22:46 netreg dhcpd: DHCPREQUEST for 10.4.4.254 (127.0.0.1)
>>>>
>>>>
>>>>from 00:03:47:e5:cb:b8 (test1) via eth0
>>>
>>>
>>>> Aug 6 13:22:46 netreg dhcpd: DHCPACK on 10.4.4.254 to
>>>>00:03:47:e5:cb:b8 (test1) via eth0
>>>>
>>>>We have checked all files for anomalies but have come up short of a
>>>>solution.
>>>>
>>>>the dchpd.conf as follows:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>## Modified: 20010813
>>>>>
>>>>>
>>>>>max-lease-time 120;
>>>>>default-lease-time 120;
>>>>>allow bootp;
>>>>>allow booting;
>>>>>option domain-name "stmartin.edu";
>>>>>option netbios-node-type 8;
>>>>>server-identifier netreg.stmartin.edu;
>>>>>ddns-update-style ad-hoc;
>>>>>ddns-updates off;
>>>>>omapi-port 7911;
>>>>>
>>>>>subnet 10.4.0.0 netmask 255.255.0.0 {
>>>>> authoritative;
>>>>> option subnet-mask 255.255.0.0;
>>>>> option broadcast-address 10.4.255.255;
>>>>> # Unknown clients get this pool.
>>>>> pool {
>>>>> range 10.4.254.1 10.4.254.254;
>>>>> option domain-name-servers 10.4.0.150;
>>>>> max-lease-time 120;
>>>>> default-lease-time 120;
>>>>> allow unknown clients;
>>>>> }
>>>>> # Known clients get this pool.
>>>>> pool {
>>>>> option domain-name-servers 10.0.0.17, 10.0.0.23;
>>>>> option routers 10.4.0.1;
>>>>> max-lease-time 28800;
>>>>> default-lease-time 28800;
>>>>> range 10.4.1.1 10.4.4.254;
>>>>> deny unknown clients;
>>>>> }
>>>>>}
>>>>>
>>>>>
>>>>>host dtroyer-1 { hardware ethernet 00:03:47:E5:CB:B8 ; ddns-hostname
>>>>>dtroyer-1;}#Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
>>>>>5.1)#20040806 13:16:07#10.4.254.254
>>>>>[root@netreg dhcpd]#
>>>>>
>>>>>
>>>>>
>>>>>
>>>>the named.conf is as follows:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>// named.conf for NetReg
>>>>>// Belongs at /etc/named.conf
>>>>>
>>>>>//server 10.4.0.150{
>>>>>// bogus yes;
>>>>>//};
>>>>>
>>>>>options {
>>>>> directory "/etc/";
>>>>> recursion no;
>>>>> fetch-glue no;
>>>>>};
>>>>>
>>>>>zone "." in {
>>>>> type master;
>>>>> file "db.root";
>>>>>};
>>>>>[root@netreg dhcpd]#
>>>>>
>>>>>
>>>>>
>>>>>
>>>>the db.root as follows:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>; Bind 8 -- Zone file -- for NetReg
>>>>>; Belongs at /etc/db.root
>>>>>
>>>>>$TTL 3600
>>>>>
>>>>>. IN SOA netreg.stmartin.edu. root.netreg.stmartin.edu. (
>>>>> 2 10800 3600 604800 86400 )
>>>>> IN NS netreg.stmartin.edu.
>>>>>; netreg 86400 IN A 10.4.0.150
>>>>>*. 86400 IN A 10.4.0.150
>>>>>
>>>>>[root@netreg dhcpd]#
>>>>>
>>>>>
>>>>>
>>>>>
>>>>the tail of the leases file as follows:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>lease 10.4.4.254 {
>>>>> starts 5 2004/08/06 20:22:41;
>>>>> ends 6 2004/08/07 04:22:41;
>>>>> binding state active;
>>>>> next binding state free;
>>>>> hardware ethernet 00:03:47:e5:cb:b8;
>>>>> uid "\001\000\003G\345\313\270";
>>>>> client-hostname "test1";
>>>>>}
>>>>>lease 10.4.4.254 {
>>>>> starts 5 2004/08/06 20:22:46;
>>>>> ends 6 2004/08/07 04:22:46;
>>>>> binding state active;
>>>>> next binding state free;
>>>>> hardware ethernet 00:03:47:e5:cb:b8;
>>>>> uid "\001\000\003G\345\313\270";
>>>>> client-hostname "test1";
>>>>>}
>>>>>[root@netreg root]#
>>>>>
>>>>>
>>>>>
>>>>>
>>>>The G5 receives dhcp from our main network just fine. But using the
>>>>netreg server, it will not accept the DHCPOFFER from the netreg server.
>>>>
>>>>Anyone have these or similar problems?
>>>>
>>>>Any information is welcome since i am the one of the 2 programmers here
>>>>at Saint Martin's College staff.
>>>>
>>>>Sincerely,
>>>>
>>>>Doug
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>**********************************************************************
>>>>To unsubscribe from this list, send an e-mail message to
>>>>majordomo@southwestern.edu containing a single line with the words:
>>>>unsubscribe netreg
>>>>Send requests for assistance to: owner-netreg@southwestern.edu
>>>>**********************************************************************
>>>>
>>>>
>>>>
>>>>
>>>>
>>>**********************************************************************
>>>To unsubscribe from this list, send an e-mail message to
>>>majordomo@southwestern.edu containing a single line with the words:
>>>unsubscribe netreg
>>>Send requests for assistance to: owner-netreg@southwestern.edu
>>>**********************************************************************
>>>
>>>
>>>
>>>
>>>
>>**********************************************************************
>>To unsubscribe from this list, send an e-mail message to
>>majordomo@southwestern.edu containing a single line with the words:
>>unsubscribe netreg
>>Send requests for assistance to: owner-netreg@southwestern.edu
>>**********************************************************************
>>
>>
>>
>**********************************************************************
>To unsubscribe from this list, send an e-mail message to
>majordomo@southwestern.edu containing a single line with the words:
>unsubscribe netreg
>Send requests for assistance to: owner-netreg@southwestern.edu
>**********************************************************************
>
>
>
-- 73 & Sincerely,Doug
Astopulse and SETI participant (SETItroyer) "Reach for the stars, they are waiting for an answer!" KE7BBV@thetroyers.org doug@thetroyers.org
********************************************************************** To unsubscribe from this list, send an e-mail message to majordomo@southwestern.edu containing a single line with the words: unsubscribe netreg Send requests for assistance to: owner-netreg@southwestern.edu **********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:47 CDT