Mailinglist Archive: opensuse-bugs (6759 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=727870

https://bugzilla.novell.com/show_bug.cgi?id=727870#c0


           Summary: Every FIND or BROWSE or LOCATE button that is meant to
                    late another PC's Services has never Worked
    Classification: openSUSE
           Product: openSUSE 11.3
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 11.3
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: scott@xxxxxxxxxxx
         QAContact: jsrain@xxxxxxxx
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101
Firefox/7.0.1

I never did report this bug as I thought this particular function just plain
old never did work in the first place in Suse Linux 10.0 and has never changed.
The problem is best shown in examples as the same problem type extends
throughout most all of YAST function where there is a server service and a
client service.
Yast sets up many types of 'server' roles, yet to locate via the browse,
lookup, find button never reveals the 'server' role that is running on the
network. I have always used the 'server role' IP number which makes just about
all Server/Client Services work.
I wrongly assumed that entering the 'server role' IP's address in all
instances, as it works and never thought that 'server role' could be located by
hostname via browse.
For those that know me you may now understand why I hate DHCP as the standard
as mappings can move, but static IP's offer a unique and reliable way of
finding any 'server role' type
I'll attach a lot of screen shots and due to the enormous impact this has
throughout Yast ask me to test a scenario and then ask me for a particular log
by name. I'm obviously not going to test all these type actions in Yast, as
this is a job for QA before RC has been authorised.
In all circumstances I have checxked and checked that the issue is NOT the
firewall beiung closed, however, as in NIS the UI does not open the firewall
fore that service, I do it manually

Reproducible: Always

Steps to Reproduce:
1.I have a NFS Server running on IP 192.168.1.20
2.I setup a NFS Client and IF I enter the Servers IP above I see the
directories.
3.If I use the 'Choose' button no NFS Servers are found in the first instance.
THE FIREWALL IS NEVER THE PROBLEM -  the error response is erroneous always,
always, always. 
Actual Results:  
Every single server, client, or locate printer or locate host in Yast fails and
has never work as tested on my network since Suse Linux 10.0 to current.
WHO tests this stuff before signoff???

Expected Results:  
The Browse, Locate, find, chose option should actually work and should have
been tested in just about ALL Yast Application where a bilateral relationship
exists or is trying to be created. - I'm only getting started...stay chewned
for Samba Server with a MS Workgroup disaster, as well as NIS, LDAP, Network
Printer.....

My hope is that this can be very quickly resolved globally in all Yast
application as I would expect the same code routine 'to discover host/client'
is just copied and pasted into everything - hence if it did not work in the
first instance, it does not work in anything. - The is really ugly to get to RC
in 11-3 and not to function - Sorry guys - This does my head in :-0

Its broken in ALL Yast Application that use any form of 'locate or scan the
network or scan for hosts...etc - Its impact is huge and this single problem
could well be why most users dont even bother to setup much past NFS
Server/Client - Try getting NIS to work! or even better SAMBA in a workgroup
only config.

Ask for anything specifically, I will happily test and send you anything you
may need to fix this

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.