http://forums.novell.com/ en Sat, 21 Nov 2009 15:20:24 GMT vBulletin 60 http://forums.novell.com/images/ca_serenity/misc/rss.jpg http://forums.novell.com/ http://forums.novell.com/novell-product-support-forums/netware/nw-other/dns-dhcp/393425-1-dhcp-server-2-vlans.html Fri, 20 Nov 2009 17:30:29 GMT I have a nW 6.5 sp7 server for DHCP. We use 172.17.x.x internally. I am trying to ad a vlan with 10.0.1.x scheme. When testing one of the ports... I have a nW 6.5 sp7 server for DHCP. We use 172.17.x.x internally. I am trying to ad a vlan with 10.0.1.x scheme.

When testing one of the ports on our switch, I do see that a DHCPDISCOVER and a DHCPOFFER. I do not ever see the DHCPREQUEST or DHCPACK, so my client does not get the 10.0.1.x address. My vlan seems to bet setup correctly. I have the DHCP Relay setup and pointing to my DHCP server at 172.17.1.5.

Can not figure out why my client is not getting the DHCP packets back.

Here is a copy of the request I see:

ping:sendto addr=10.0.1.3
AMAGet() exit err:0, subnet:10.0.1.0, addr:10.0.1.2
2009/11/20 11:04:20 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:04:20 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>.
AMAGet() exit err:0, subnet:10.0.1.0, addr:10.0.1.2
2009/11/20 11:04:28 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:04:28 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>.

AMAGet() exit err:0, subnet:10.0.1.0, addr:10.0.1.2
2009/11/20 11:04:43 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:04:43 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>.
2009/11/20 11:05:23 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:05:23 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>.

AMAGet() exit err:0, subnet:10.0.1.0, addr:10.0.1.2
2009/11/20 11:05:31 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:05:31 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>.
AMAGet() exit err:0, subnet:10.0.1.0, addr:10.0.1.2
2009/11/20 11:05:47 <DHCPDISCOVER> packet received from client <0:14:22:B8:E4:6C>.
2009/11/20 11:05:47 Sending BOOTP/DHCP reply <DHCPOFFER> to <0:14:22:B8:E4:6C> as <10.0.1.1>. ]]> Dns-Dhcp mgh2468 http://forums.novell.com/novell-product-support-forums/netware/nw-other/dns-dhcp/393425-1-dhcp-server-2-vlans.html http://forums.novell.com/novell-product-support-forums/netware/nw-other/dns-dhcp/392148-warning-zone-xxxx-xxx-expired.html Tue, 10 Nov 2009 16:19:51 GMT I have a Microsoft DNS server hosting a primary domain which syncs with a NetWare Secondary DNS server. The Netware is a Designated Primary server... I have a Microsoft DNS server hosting a primary domain which syncs with a NetWare Secondary DNS server. The Netware is a Designated Primary server with a zone, itself. In the Netware setup, I also have 10 authoritative DNS servers (Passive primary and Passive Secondary for the MS zone) that are DNS servers for remote sites. Name resolution works fine.

On the Netware server (Passive DNS servers) I loaded NAMED.NLM with the switch "-S". I now see that the remote servers are displaying "Warning: ZONE xxxx.xxx/IN: expired" where xxxx.xxx is the Microsoft ZONE. The designated Primary Netware DNS server does not get the warning, in fact, when using "-ZI zone.name" it shows successful. When doing the same command, on the remote sites, you get a "Failed, zone is not secondary or server is not designated for this zone"....

Config:
Netware 6.5Sp7
named.nlm ver 6.06.03
]]> Dns-Dhcp pje7 http://forums.novell.com/novell-product-support-forums/netware/nw-other/dns-dhcp/392148-warning-zone-xxxx-xxx-expired.html