Question : Problems logging into novell when client moved to new vlan and switched to dhcp.

We recently started having problems with the novell client not being able to find the tree for workstations moved to an internal vlan that is not within the same vlan as the novell server. we are using a windows 2003 dhcp server. If the machine dhcp's within the same network as the novell server (strictly IP) it's fine  but if it dhcps inside a different vlan it seems it can't find the tree. If i punch in the IP of the server it can login but i cannot browse the tree or login to the erver via dns name, only IP. not every machine is having this problem and we've replicated it with 4.91 sp3 and sp3 and can't seem to find out what client setting is different on our working machines. Is there some addiction dhcp options we need to add into the windows dhcp server to help the novell?

Answer : Problems logging into novell when client moved to new vlan and switched to dhcp.

>>Do you know how to make a tree resovlable via dns? Do you just take the tree name and assign it to one of the novell servers?  Our server is already setup with dns so that works ok.<<

Yes, I know how.

You already have an A record with the hostname of the NetWare server resolving to the IP address of the server, correct?  Simply add another A record in the same zone, pointing to the same IP address, with a hostname of the tree name.  

If you've got your DNS on Windows also, you should then follow up with verifying/creating a reverse-lookup PTR.  You did create a reverse-lookup zone, correct?

Note that if you want to use DNS for your primary name resolution in the Novell client, you'll want to pare back on the other methods, like I mentioned earlier.