Topic
  • 9 replies
  • Latest Post - ‏2006-11-10T12:39:17Z by SystemAdmin
SystemAdmin
SystemAdmin
47283 Posts

Pinned topic Disable netbios over TCP/IP problems with albd_server

‏2006-11-09T09:57:25Z |
Hello !

We have windows xp(sp2) with cc 2002.05.
(No active directory, 2000 domain)

To start a .exe in a view takes very long time (15sec). I have read
in another user group to disable the netbios over tcp/ip.
Wow...now we have a top speed, but after a reboot the albd_server
will not start.
Error Received NULL CLEARCASE SID, couldn´t register mfvs.

Does anybody know, is netbios needed ? Any reason why the albd will not start ??

Thanks for your help

Greetings
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Disable netbios over TCP/IP problems with albd_server

    ‏2006-11-09T12:37:15Z  
    prebilly1212 wrote:
    > We have windows xp(sp2) with cc 2002.05.
    > (No active directory, 2000 domain)
    >
    > To start a .exe in a view takes very long time (15sec). I have read
    > in another user group to disable the netbios over tcp/ip.
    > Wow...now we have a top speed, but after a reboot the albd_server
    > will not start.
    > Error Received NULL CLEARCASE SID, couldn´t register mfvs.
    >
    > Does anybody know, is netbios needed ? Any reason why
    > the albd will not start ??

    Google finds an IBM Technote on this issue ("cccredmgr: Error:
    Received NULL CLEARCASE SID, couldn't register with MVFS",
    reference # 1129874,
    http://www-1.ibm.com/support/docview.wss?uid=swg21129874).

    Even if that helps you to get past the immediate problem, I'd
    be surprised if you can get by without Netbios in a non-AD
    domain. We have an AD domain and we found that ClearCase
    worked without Netbios, but some other services did not.

    If you have problems disabling Netbios, I think the next best
    option is to configure your client machines as Netbios P-nodes.
    See
    http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13818749&thread=118227&forum=333
    That's what we have done and it has worked very well for us.

    Regards,
    Patrick Hyland.[/pre]
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re:Re: Disable netbios over TCP/IP problems with albd_server

    ‏2006-11-09T17:53:16Z  
    prebilly1212 wrote:
    > We have windows xp(sp2) with cc 2002.05.
    > (No active directory, 2000 domain)
    >
    > To start a .exe in a view takes very long time (15sec). I have read
    > in another user group to disable the netbios over tcp/ip.
    > Wow...now we have a top speed, but after a reboot the albd_server
    > will not start.
    > Error Received NULL CLEARCASE SID, couldn´t register mfvs.
    >
    > Does anybody know, is netbios needed ? Any reason why
    > the albd will not start ??

    Google finds an IBM Technote on this issue ("cccredmgr: Error:
    Received NULL CLEARCASE SID, couldn't register with MVFS",
    reference # 1129874,
    http://www-1.ibm.com/support/docview.wss?uid=swg21129874).

    Even if that helps you to get past the immediate problem, I'd
    be surprised if you can get by without Netbios in a non-AD
    domain. We have an AD domain and we found that ClearCase
    worked without Netbios, but some other services did not.

    If you have problems disabling Netbios, I think the next best
    option is to configure your client machines as Netbios P-nodes.
    See
    http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13818749&thread=118227&forum=333
    That's what we have done and it has worked very well for us.

    Regards,
    Patrick Hyland.[/pre]

    Not sure whether it's relevant here, but added:

    127.0.0.1 view # ClearCase views.

    to my hosts file:

    c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS

    That made a big perf diff, also...
    (Though mostly in the Windows Explorer.)

    FWIW...

    Patrick_Hyland
    <disadmin@us.ibm.
    com> To
    Sent by: cciug@lists.ca.ibm.com
    cciug-bounces@lis cc
    ts.ca.ibm.com
    Subject
    cciug Re: Disable netbios over
    11/09/2006 07:48 TCP/IP problems with albd_server
    AM
    Please respond to
    cciug@lists.ca.ib
    m.com
    billy1212 wrote:
    > We have windows xp(sp2) with cc 2002.05.
    > (No active directory, 2000 domain)
    >
    > To start a .exe in a view takes very long time (15sec). I have read
    > in another user group to disable the netbios over tcp/ip.
    > Wow...now we have a top speed, but after a reboot the albd_server
    > will not start.
    > Error Received NULL CLEARCASE SID, couldn´t register mfvs.
    >
    > Does anybody know, is netbios needed ? Any reason why
    > the albd will not start ??

    Google finds an IBM Technote on this issue ("cccredmgr: Error:
    Received NULL CLEARCASE SID, couldn't register with MVFS",
    reference # 1129874,
    http://www-1.ibm.com/support/docview.wss?uid=swg21129874).

    Even if that helps you to get past the immediate problem, I'd
    be surprised if you can get by without Netbios in a non-AD
    domain. We have an AD domain and we found that ClearCase
    worked without Netbios, but some other services did not.

    If you have problems disabling Netbios, I think the next best
    option is to configure your client machines as Netbios P-nodes.
    See
    http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13818749&thread=118227&forum=333

    That's what we have done and it has worked very well for us.

    Regards,
    Patrick Hyland.

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    http://att1.html
    http://graycol.gif
    http://pic28321.gif
    http://ecblank.gif
    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com

    Attachment not added (too many attachments): "pic28321.gif"
    Attachment not added (too many attachments): "ecblank.gif"
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Re:Re: Disable netbios over TCP/IP problems with albd_server

    ‏2006-11-10T01:14:36Z  

    Not sure whether it's relevant here, but added:

    127.0.0.1 view # ClearCase views.

    to my hosts file:

    c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS

    That made a big perf diff, also...
    (Though mostly in the Windows Explorer.)

    FWIW...

    Patrick_Hyland
    <disadmin@us.ibm.
    com> To
    Sent by: cciug@lists.ca.ibm.com
    cciug-bounces@lis cc
    ts.ca.ibm.com
    Subject
    cciug Re: Disable netbios over
    11/09/2006 07:48 TCP/IP problems with albd_server
    AM
    Please respond to
    cciug@lists.ca.ib
    m.com
    billy1212 wrote:
    > We have windows xp(sp2) with cc 2002.05.
    > (No active directory, 2000 domain)
    >
    > To start a .exe in a view takes very long time (15sec). I have read
    > in another user group to disable the netbios over tcp/ip.
    > Wow...now we have a top speed, but after a reboot the albd_server
    > will not start.
    > Error Received NULL CLEARCASE SID, couldn´t register mfvs.
    >
    > Does anybody know, is netbios needed ? Any reason why
    > the albd will not start ??

    Google finds an IBM Technote on this issue ("cccredmgr: Error:
    Received NULL CLEARCASE SID, couldn't register with MVFS",
    reference # 1129874,
    http://www-1.ibm.com/support/docview.wss?uid=swg21129874).

    Even if that helps you to get past the immediate problem, I'd
    be surprised if you can get by without Netbios in a non-AD
    domain. We have an AD domain and we found that ClearCase
    worked without Netbios, but some other services did not.

    If you have problems disabling Netbios, I think the next best
    option is to configure your client machines as Netbios P-nodes.
    See
    http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13818749&thread=118227&forum=333

    That's what we have done and it has worked very well for us.

    Regards,
    Patrick Hyland.

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    http://att1.html
    http://graycol.gif
    http://pic28321.gif
    http://ecblank.gif
    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com

    Attachment not added (too many attachments): "pic28321.gif"
    Attachment not added (too many attachments): "ecblank.gif"
    prematthew.miner wrote:
    > Not sure whether it's relevant here, but added:
    >
    > 127.0.0.1 view # ClearCase
    > views.
    >
    > to my hosts file:
    >
    > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    >
    > That made a big perf diff, also...

    Hello Matthew,
    that's a good point. This optimization comes up fairly
    often and I assumed, for no good reason, that 'billy1212'
    already had it in place. BTW, it may help to put
    the entry '127.0.0.1 view #pre' in the LMHOSTS file too. See
    http://www-1.ibm.com/support/docview.wss?uid=swg21134735
    for more details (but ignore the rubbish about restarting
    the machine; just run 'nbtstat -R' at the command prompt
    to refresh the name cache).

    The 'view' entry in the hosts files helps because ClearCase
    has long had a (mis-)feature whereby it sometimes causes Windows
    to search for a host called 'view' on the network.

    Windows XP SP2 introduced a new problem, at least for some
    people. When a view is being accessed it sometimes causes
    Windows to search for a host with the same name as the
    view on the network. The problem can be fixed in the same
    way as the 'view' problem by putting an entry for every view
    accessed on a machine in the hosts files. That seems
    impractical though, so it is necessary to find other ways
    to short circuit the host search mechanisms. The main causes
    of delays in the host searches are the timeouts associated
    with NetBIOS broadcasts, so it helps a lot if you can
    disable the broadcasts. Disabling NetBIOS, if you can get
    away with it, disables the broadcasts. Converting clients
    to P-nodes also disables the broadcasts, though you still
    get (very much smaller) delays associated with WINS
    lookups.

    Regards,
    Patrick[/pre]
  • dsb
    dsb
    75 Posts

    Re:Re: Re:Re: Disable netbios over TCP/IP problems with albd_server

    ‏2006-11-10T05:29:47Z  
    prematthew.miner wrote:
    > Not sure whether it's relevant here, but added:
    >
    > 127.0.0.1 view # ClearCase
    > views.
    >
    > to my hosts file:
    >
    > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    >
    > That made a big perf diff, also...

    Hello Matthew,
    that's a good point. This optimization comes up fairly
    often and I assumed, for no good reason, that 'billy1212'
    already had it in place. BTW, it may help to put
    the entry '127.0.0.1 view #pre' in the LMHOSTS file too. See
    http://www-1.ibm.com/support/docview.wss?uid=swg21134735
    for more details (but ignore the rubbish about restarting
    the machine; just run 'nbtstat -R' at the command prompt
    to refresh the name cache).

    The 'view' entry in the hosts files helps because ClearCase
    has long had a (mis-)feature whereby it sometimes causes Windows
    to search for a host called 'view' on the network.

    Windows XP SP2 introduced a new problem, at least for some
    people. When a view is being accessed it sometimes causes
    Windows to search for a host with the same name as the
    view on the network. The problem can be fixed in the same
    way as the 'view' problem by putting an entry for every view
    accessed on a machine in the hosts files. That seems
    impractical though, so it is necessary to find other ways
    to short circuit the host search mechanisms. The main causes
    of delays in the host searches are the timeouts associated
    with NetBIOS broadcasts, so it helps a lot if you can
    disable the broadcasts. Disabling NetBIOS, if you can get
    away with it, disables the broadcasts. Converting clients
    to P-nodes also disables the broadcasts, though you still
    get (very much smaller) delays associated with WINS
    lookups.

    Regards,
    Patrick[/pre]
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Performace, DNS, hosts, lmhosts, list of recommended practices.

    ‏2006-11-10T07:10:32Z  
    • dsb
    • ‏2006-11-10T05:29:47Z
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com

    Good ideas, gents, wish I'd thought of them :-)

    So, David, I guess that;'s your answer - we ( I ) didn't think of it...

    My Quick Refernce Card (which covers the install, among other things)
    actually mentions adding the entry to the hosts file (it made such a big
    diff). Adding to the DNS instead would allow me to take that step out......

    Has anyone ever compiled a list of bullet points of things that
    could/should be done in a CC installation?
    e.g., covering performance, recommended practices (such as reassigning
    ownership of an element), etc.?
    I went to most of the training for CC back in Rational days, and while it
    was useful, it barely scratched the surface of what's needed (and been
    brought up in this forum).

    I am thinking sort of along the lines of a "Release Notes" kind of
    document, with bulllet points, so that one could read it to pick and choose
    what's useful for their site. It might be long and tedious to go through,
    but at the end of the day/week/month/whatever, a CC Admin would know how to
    address a lot of issues, and where to find solutions to a lot more (when/if
    they arise). All this without having to reinvent several wheels and
    discover many things the hard way.

    Perhaps an addition to ClearCase wiki entry? (BTW, the wiki entry at
    http://en.wikipedia.org/wiki/Clearcase is a pretty thorough, but
    short/concise, overview of CC). The See Also links there also point to
    comparison pages (CC vs. you-name-it), etc.

    Hmmm...



    Procrastinator's Paradox: The easiest thing about procrastinating is
    getting started.
    • Richard Munitz

    David Boyce
    <dsb@boyski.com>
    Sent by: To
    cciug-bounces@lis cciug@lists.ca.ibm.com
    ts.ca.ibm.com cc

    Subject
    11/10/2006 12:39 Re: cciug Re: Re:Re: Disable
    AM netbios over TCP/IP problems
    with albd_server
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    http://att1.html
    http://graycol.gif
    http://pic09314.gif
    http://ecblank.gif
    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com

    Attachment not added (too many attachments): "pic09314.gif"
    Attachment not added (too many attachments): "ecblank.gif"
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Re:Re: Re:Re: Disable netbios over TCP/IP problems<br> with albd_server

    ‏2006-11-10T07:23:26Z  
    • dsb
    • ‏2006-11-10T05:29:47Z
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    Hello!
    The only solution is to entry the view names in the lmhosts file with #PRE load settings. The entry in the host file is only for the fast display if you click on the view.
    Thats what we have found out.
    I think its only a workaround...host,lmhost and so on. Normally we don´t want to use this stuff !!
    I think to work with CC (v5) under XP is really a problem !

    Does anybody know, how clearcase works with the verion v7. Are there also such "bugs" like v5 or v6.

    Greetings
  • SystemAdmin
    SystemAdmin
    47283 Posts

    RE:Re: Performace, DNS, hosts, lmhosts, list of recommended practices.

    ‏2006-11-10T09:52:06Z  

    Good ideas, gents, wish I'd thought of them :-)

    So, David, I guess that;'s your answer - we ( I ) didn't think of it...

    My Quick Refernce Card (which covers the install, among other things)
    actually mentions adding the entry to the hosts file (it made such a big
    diff). Adding to the DNS instead would allow me to take that step out......

    Has anyone ever compiled a list of bullet points of things that
    could/should be done in a CC installation?
    e.g., covering performance, recommended practices (such as reassigning
    ownership of an element), etc.?
    I went to most of the training for CC back in Rational days, and while it
    was useful, it barely scratched the surface of what's needed (and been
    brought up in this forum).

    I am thinking sort of along the lines of a "Release Notes" kind of
    document, with bulllet points, so that one could read it to pick and choose
    what's useful for their site. It might be long and tedious to go through,
    but at the end of the day/week/month/whatever, a CC Admin would know how to
    address a lot of issues, and where to find solutions to a lot more (when/if
    they arise). All this without having to reinvent several wheels and
    discover many things the hard way.

    Perhaps an addition to ClearCase wiki entry? (BTW, the wiki entry at
    http://en.wikipedia.org/wiki/Clearcase is a pretty thorough, but
    short/concise, overview of CC). The See Also links there also point to
    comparison pages (CC vs. you-name-it), etc.

    Hmmm...



    Procrastinator's Paradox: The easiest thing about procrastinating is
    getting started.
    • Richard Munitz

    David Boyce
    <dsb@boyski.com>
    Sent by: To
    cciug-bounces@lis cciug@lists.ca.ibm.com
    ts.ca.ibm.com cc

    Subject
    11/10/2006 12:39 Re: cciug Re: Re:Re: Disable
    AM netbios over TCP/IP problems
    with albd_server
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    http://att1.html
    http://graycol.gif
    http://pic09314.gif
    http://ecblank.gif
    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com

    Attachment not added (too many attachments): "pic09314.gif"
    Attachment not added (too many attachments): "ecblank.gif"
    Here's my list:

    For installation (on Windows platform), use the silent install
    script I gave to you. (This script takes care of stopping antivirus and
    assigning TMP and TEMP to make sure that Windows installer does not
    choke on blanks in their values, and then runs the installer
    appropriately.)
    After installation and reboot (on Windows platform), or after
    any major upgrade, run the script I gave to you. (This script sets
    CLEARCASE_PROMARY_GROUP, defines additional shortcuts for ClearCase
    Explorer, and modifies context menus for ClearCase explorer and Windows
    Explorer -- I had to add some more tools in them.)
    Read my instructions on how to interpret ClearCase Doctor
    analysis (at first startup after reboot).
    Ensure that antivirus software is not scanning network devices
    (such as \\view).
    Disable offline files in Windows.
    Add the hostname "view" to hosts file (yes, David's comment was
    a good one!)
    Read my instructions on connecting/disconnecting laptop to/from
    network.
    Read my instructions on placing snapshot views so that they will
    not be included in backup unnnecessarily.

    My instructions for uninstall are shorter.

    Heini
    ________________________________

    From: cciug-bounces@lists.ca.ibm.com
    mailto:cciug-bounces@lists.ca.ibm.com
    Sent: 10 November, 2006 09:11
    To: cciug@lists.ca.ibm.com
    Subject: cciug Re: Performace, DNS, hosts, lmhosts,list of
    recommended practices.

    Has anyone ever compiled a list of bullet points of things that
    could/should be done in a CC installation?
    e.g., covering performance, recommended practices (such as
    reassigning ownership of an element), etc.?
    http://att1.html
    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Re:Re: Re:Re: Disable netbios over TCP/IP problems<br> with albd_server

    ‏2006-11-10T12:16:27Z  
    • dsb
    • ‏2006-11-10T05:29:47Z
    At 08:14 PM 11/9/2006, Patrick_Hyland wrote:
    >matthew.miner wrote:
    > > Not sure whether it's relevant here, but added:
    > >
    > > 127.0.0.1 view # ClearCase
    > > views.
    > >
    > > to my hosts file:
    > >
    > > c:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS
    > >
    > > That made a big perf diff, also...

    It's getting a bit off the track, but I've often wondered why people
    don't just solve this site-wide by putting the same setting in their
    local DNS. It would be marginally slower than the host file, in the
    same way that all DNS usage is slower than a host file, but that's
    the point of DNS - to keep you from having to keep lots of host files
    in sync. Most people find it's worth the cost.

    In addition to making per-workstation hacks unnecessary, this has the
    added benefit of making it harder for some person in IT who knows
    nothing about ClearCase to name an actual machine "view". I could
    easily see someone thinking - and not without reason - that it would
    make a good name for a view server.

    >The problem can be fixed in the same
    >way as the 'view' problem by putting an entry for every view
    >accessed on a machine in the hosts files. That seems
    >impractical though...

    Potentially you could have a nightly, or hourly, script which takes
    the output of lsview, massages it into the right format, and sticks
    it in DNS as above. But most likely the other solutions you note are
    more robust.

    -David Boyce

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
    preDavid Boyce wrote:
    > ... I've often wondered why people don't just solve this [need
    > to have host name "view" resolve to "127.0.0.1"] site-wide
    > by putting the same setting in their local DNS.

    David,
    that's a good idea. Unfortunately, it's not so straightforward
    for some of us. Our DNS infrastructure is half way across the
    continent, and soon will be half way across the world. We have
    no control over it. Providing a script that people can run as
    part of a ClearCase installation to edit the 'hosts' and 'lmhosts'
    files (and do other grimy stuff) is a much more practical option
    for us than trying to get changes made to the central infrastructure
    so support our (tiny minority) requirements.

    BTW, I think that if you can get a DNS entry set up it needs to be
    for a fully qualified domain name (e.g. 'view.xxx.yyy.com') instead
    of just 'view'. A quick spin on Ethereal suggests that Windows
    XP always appends entries from the DNS suffix list before submitting
    queries for bare host names to DNS.

    Regards,
    Patrick[/pre]
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: Re:Re: Re:Re: Disable netbios over TCP/IP problems<br> with albd_server

    ‏2006-11-10T12:39:17Z  
    Hello!
    The only solution is to entry the view names in the lmhosts file with #PRE load settings. The entry in the host file is only for the fast display if you click on the view.
    Thats what we have found out.
    I think its only a workaround...host,lmhost and so on. Normally we don´t want to use this stuff !!
    I think to work with CC (v5) under XP is really a problem !

    Does anybody know, how clearcase works with the verion v7. Are there also such "bugs" like v5 or v6.

    Greetings
    prebilly1212 wrote
    > The only solution [to prevent Windows XP SP2 searching the network
    > for hosts with the same names as dynamic views] is to entry the view
    > names in the lmhosts file with #PRE load settings. The entry in
    > the host file is only for the fast display if you click on the view.

    That is disappointing. Changing the clients to NetBIOS P-nodes worked
    very well for us. What happened when you tried it?
    The only reason I can think why it might not work is if your WINS
    servers are not working correctly: in which case you would suffer
    WINS connection timeouts, and worse if you have no functioning
    WINS servers at all. If that is the case, you should look at getting
    it fixed because you really don't want to be dependent on
    broadcasting for NetBIOS name resolution.

    The fact that 'lmhosts' entries work and 'hosts' entries do not
    does not surprise me. Windows has a bewildering variety of ways
    of doing name resolution, and I've never seen a credible
    explanation of what determines the order in which the various
    methods are tried. I suspect that in some circumstances it is
    exhausting all NetBios-related methods before looking at
    'hosts' and DNS. You could try disabling 'lmhosts', but I
    doubt if it would make the 'hosts' entries effective.

    If putting entries in 'lmhosts' for the views is your only
    option, you might want to consider providing a script that
    clients can run from a scheduled task to automate the process
    of updating 'lmhosts' and (for safety) 'hosts' and running
    'nbtstat -R'.

    Regards,
    Patrick Hyland.[/pre]