Home Network and NETBUEI

[Gerald Fay]

I can get computers on our small home network to see each other
and share files, however, I cannot ping other computers and I
had to add the NETBUEI protocol to get things to work.

I have 2 laptops with XPhome and 1 desktop with XPPro. All are
using the same workgroup MSHOME.

The DHCP Server is a Wireless Linksys Router. IP Addresses are
not fixed. All 3 machines are using Windows OneCare as the
Firewall/Antivirus.

Is it possible to connect this Workgroup without NETBUEI?

Thanks

 

[David H. Lipman]

From: "Gerald Fay" <[email protected]>

| I can get computers on our small home network to see each other
| and share files, however, I cannot ping other computers and I
| had to add the NETBUEI protocol to get things to work.
|
| I have 2 laptops with XPhome and 1 desktop with XPPro. All are
| using the same workgroup MSHOME.
|
| The DHCP Server is a Wireless Linksys Router. IP Addresses are
| not fixed. All 3 machines are using Windows OneCare as the
| Firewall/Antivirus.
|
| Is it possible to connect this Workgroup without NETBUEI?
|
| Thanks

NetBEUI is a NetBIOS like protocol with its own transport.

You should be using NetBIOS over IP ONLY. Since you are behind a Router, this makes the MS
Networking much safer when connecting to the Internet.

All computers do not have to be in the same WorkGroup, albeit it makes it easier.

OneCare is junk. There are much better solutions out there. Even Free ones are better !

OneCare has a FireWall and you should make sure NetBIOS over IP is allowed through it
(TCP/UDP ports 135 ~ 139 and 445). If all the nodes are using NetBIOS over IP, are
receiving an IP address from the Router and can communicate with the Router and Internet
then MS Networking should work.

Remove NetBEUI.

Remember: If you don't secure the Wireless network, you are SCREWED !

As always, I suggest specifically blocking TCP/UDP ports 135 ~ 139 and 445 on *any* SOHO
Router.

 

[Gerald Fay]

Newsgroups: microsoft.public.windowsxp.help_and_support

If the Home Workstation is working properly, shouldn't I be
able to ping machines on the network? I cannot.

As always, I suggest specifically blocking TCP/UDP ports 135 ~ 139 and 445 on *any* SOHO
Router.

Are you saying to allow these ports in OneCare (for local
network use), but block them on the Linksys (to Internet)
router side? If so, shouldn't OneCare be already configured for
use of ports for NetBios?

 

[David H. Lipman]

From: "Gerald Fay" <[email protected]>

Replies are inline...


| If the Home Workstation is working properly, shouldn't I be
| able to ping machines on the network? I cannot.


Not if the FireWall application within OneCare is blocking pings !


||
| Are you saying to allow these ports in OneCare (for local
| network use), but block them on the Linksys (to Internet)
| router side? If so, shouldn't OneCare be already configured for
| use of ports for NetBios?

Yes. Block the posts on the perimeter of the LAN/WAN interface and allow the NetBIOS over
IP ports on the LAN such that MS Networking works properly.

My suggestion would NOT be using OneCare at all. I have repeatedly tested their AV solution
and it falls below the AV vendor standards. As for a FireWAll application, one should ONLY
be used with knowledge of how it works in blocking network access.

Setup your LAN with NetBIOS over IP (only and NO NetBEUI) and the FireWall in OneCare
DISABLED. Once you see that MS Networking works, setup the appropriate rules to allow MS
Networking.

 

[q_q_anonymous]

David H. Lipman wrote:

NetBIOS over IP is allowed through it
(TCP/UDP ports 135 ~ 139 and 445). If all the nodes are using NetBIOS over IP, are
receiving an IP address from the Router and can communicate with the Router and Internet
then MS Networking should work.

I agree with your advice to not allow those.

But - on a technicality

isn't port 135 for "RPC", not NetBIOS/NetBT ?

port 136 - probably not used for anything standard in windows.

http://berghel.net/col-edit/digital_village/dec-05/dv_12-05.php
"Technically, ports 135 and 137-139 are used by the legacy NetBios
application programming interface while port 445 is assigned to a
network protocol called Server Message Block. While originally intended
for file and printing sharing"

That seems to indicate port 135 is for NetBT (and RPC). But, 136
isn't.

445 is certainly used potentially in file and printer sharing. (the
classic petri.co.il article discusses that)

 

[David H. Lipman]

From: "Gerald Fay" <[email protected]>

| If the Home Workstation is working properly, shouldn't I be
| able to ping machines on the network? I cannot.
||
| Are you saying to allow these ports in OneCare (for local
| network use), but block them on the Linksys (to Internet)
| router side? If so, shouldn't OneCare be already configured for
| use of ports for NetBios?

24+ hrs. later.

And the results are... ?