Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Post by Annihilato » Mon, 26 Jun 2000 04:00:00



    MCSE class knowledge is required to answer this post, so this question goes out primarily to Tim Hines, Andrej Budja, and other regular visiting professionals.

Why does >topic< occur?
Persumed answer: because NetBT gets bound to the "Internal" interface's address, and this confuses the browser.
Am I right?

How do I stop it from happening?
Persumed solution: stop NetBT from getting bound to "Internal".
If I am right, how do I do this? If not, what is the true remedy?

Thanks in advance for your answers.

--
Annihilator
Head of the SawMan's Consortium
[ http://consortium.come.to/ ]

 
 
 

Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Post by Andrej Budj » Mon, 26 Jun 2000 04:00:00


You can disable NetBIOS over TCP/IP in the TCP/IP properties, by
clicking Advanced button, and checking Disable NetBIOS over TCP/IP on
the WINS tab.

But if you have w2k clients only you don't need browsing...

Andrej
--
Andrej Budja, MCSE+I, MVP

On Sun, 25 Jun 2000 19:06:36 +0200, "Annihilator"


>    MCSE class knowledge is required to answer this post, so this question goes out primarily to Tim Hines, Andrej Budja, and other regular visiting professionals.

>Why does >topic< occur?
>Persumed answer: because NetBT gets bound to the "Internal" interface's address, and this confuses the browser.
>Am I right?

>How do I stop it from happening?
>Persumed solution: stop NetBT from getting bound to "Internal".
>If I am right, how do I do this? If not, what is the true remedy?

>Thanks in advance for your answers.


 
 
 

Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Post by Annihilato » Tue, 27 Jun 2000 04:00:00


Quote:> You can disable NetBIOS over TCP/IP in the TCP/IP properties, by

clicking Advanced button, and checking Disable NetBIOS over TCP/IP on
the WINS tab.

Quote:> But if you have w2k clients only you don't need browsing...

    Unfortunately, I often have legacy clients (W9x, NT 4) connecting, so disabling NetBIOS entirely is not an option. Is there a registry hack for disabling NetBIOS for the Internal interface?

--
Annihilator
Head of the SawMan's Consortium
[ http://consortium.come.to/ ]

 
 
 

Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Post by Andrej Budj » Tue, 27 Jun 2000 04:00:00


You disable NetBIOS per interface. What internal interface do you
mean?

Andrej
--
Andrej Budja, MCSE+I, MVP

On Mon, 26 Jun 2000 00:19:00 +0200, "Annihilator"


>    Unfortunately, I often have legacy clients (W9x, NT 4) connecting, so disabling NetBIOS entirely is not an option. Is there a registry hack for disabling NetBIOS for the Internal interface?

 
 
 

Workgroup Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

Post by Annihilato » Tue, 27 Jun 2000 04:00:00


Quote:> You disable NetBIOS per interface. What internal interface do you mean?

    "Internal" interface, the one used by RAS to hook up with the inbound caller. The IP address assigned to it is the first from the range specified to be assigned to inbound callers.
    Illustration: this is "ipconfig /all"'s output before RAS accepts an incoming call:
***
Ethernet adapter LAN:
        Connection-specific DNS Suffix  . : domain
        Description . . . . . . . . . . . : NE2000 Compatible
        Physical Address. . . . . . . . . : 00-00-01-25-21-01
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 192.168.0.1
***
    And this is after a remote access client connects, and for ever after, unless the RAS service is restarted:
***
Ethernet adapter LAN:
        Connection-specific DNS Suffix  . : domain
        Description . . . . . . . . . . . : NE2000 Compatible
        Physical Address. . . . . . . . . : 00-00-01-25-21-01
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 192.168.0.1

PPP adapter RAS Server (Dial In) Interface:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.8
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
***
^ This at the end is the interface I am referring to. Its address is the first from my assigned range (192.168.0.8-10).

    As long as this interface is active, network browsing is intolerably slow.

--
Annihilator
Head of the SawMan's Consortium
[ http://consortium.come.to/ ]

 
 
 

1. Network Browsing Slows To Crawl When Remote Access ("Internal") Interface Enabled

    MCSE class knowledge is required to answer this post, so this question goes out primarily to Tim Hines, Andrej Budja, and other regular visiting professionals.

Why does >topic< occur?
Persumed answer: because NetBT gets bound to the "Internal" interface's address, and this confuses the browser.
Am I right?

How do I stop it from happening?
Persumed solution: stop NetBT from getting bound to "Internal".
If I am right, how do I do this? If not, what is the true remedy?

Thanks in advance for your answers.

--
Annihilator
Head of the SawMan's Consortium
[ http://consortium.come.to/ ]

2. DSP56307 and C/ASM crosscompiling

3. Slow Network Browsing When Remote Access "Internal" Interface Enabled

4. Enumeration of COM Ports?

5. "memory could not be written" (or "read")

6. HTML

7. Explorer "Read" access but deny "copy" and "write"

8. Amigactive magazine

9. "Unable to add the interface Internal.." error finally solved, sorta... but....

10. "Internal" interface not getting proper IP from DHCP... it used to though???

11. RemoteAccess problems with "Internal" interface

12. assign IP to "internal" interface of NAT?

13. Updating "Internal" Interface routes