http://qa.mandrakesoft.com/show_bug.cgi?id=6068
------- Additional Comments From [EMAIL PROTECTED] 2003-05-10 14:40 ------- This is not a bug, but a bad design decision. The network wizard's most prominent name setting is for the zeroconf name, not the hostname. This issue has been discussed before on cooker, but the drakconnect maintainer refuses to discuss the design of drakconnect, and insists on only setting the zeroconf name (which should never be done) instead of the more logical hostname. This results in broken configurations for CUPS (which the CUPS maintainer has worked around), samba, apache (some redirects will point a client to localhost, which is only valid if they are running the browser on the server), postfix and a number of other network services. If you want to set your hostname with the wizard, you must run it in expert mode, and if you want to send your DHCP hostname (which is the default on Windows), you then need to fill the same hostname in in 3 places in the wizard (which is very counter-intuitive). I think there are already bugs addressing this, but it's too slow searching over a dialup connection ... -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: When using the network wizard, it asks for the computer name but does not put it in the "computer name" box in the drakconnect interface.
