http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-19 11:46 ---
Joerg, I am taking this discussion off the list so follow up via email. This
looks more like a networking issue than any type of bug, so dont want to be
flooding the
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 12:05 ---
Finally got your patch installed. A few minor things as well as some on the
addition files in the SRPM would need to be changed in order for it to work
after an RPM
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 21:43 ---
You may have the same problem as in Bug #1744. You do have 127.0.0.1 as the primary
nameserver in /etc/resolve.conf. Try removing that entry and see if you can resolve
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-11 22:19 ---
Patch looks like it should fix this. I am unable to test on this machine due to the
Kdevelop
autoconf2 conflict.
I would also like to note that I also run into the
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-10 15:11 ---
I say this is a configuration issue. The big problem I ran into was when
plugging into a network with a M$ Active Directory running as the nameserver.
When you setup
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-09 01:46 ---
I just spent the entire day today fighting with the exact same problem. upgrade from
9.0 and
same domain extension.
I have 2 domains on my local network. Systems
