Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Netbeui
- Thread starter knds1
- Start date
netmediasystems
MIS
netbeui is not a routeable protocol...so no
brian
brian
Bzzzz... wrong answer..
You can pass it several ways. You can bridge it, tunnel it, convert it, Use DLSW+ and a few others.
For this question, look at this document:
How to Enable Browsing Using NetBIOS Over IP
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
You can pass it several ways. You can bridge it, tunnel it, convert it, Use DLSW+ and a few others.
For this question, look at this document:
How to Enable Browsing Using NetBIOS Over IP
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
netmediasystems
MIS
using netbeui would not be the typical way to connect to a remote office...and it seems it is used along with ip...making it routeable
brian
brian
Brian-
It's more common then you think. Many times at the remote office you need DHCP, WINS, and network browsing for resources. Thats not counting leagcy apps that cheated by using NB for something. A pure IP network will not give you the full functionality of a Microsoft network. Which is why in 2K and more so in XP, you can kill NB if you are in a *pure* 2K or XP network. But, in the real world, the network still has 95,98, ME and NT4 so NB is a fact of life after some fashion.
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
It's more common then you think. Many times at the remote office you need DHCP, WINS, and network browsing for resources. Thats not counting leagcy apps that cheated by using NB for something. A pure IP network will not give you the full functionality of a Microsoft network. Which is why in 2K and more so in XP, you can kill NB if you are in a *pure* 2K or XP network. But, in the real world, the network still has 95,98, ME and NT4 so NB is a fact of life after some fashion.
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
netmediasystems
MIS
Mike
i understand now....it has become more of a microsoft situation!!! I confess, i am terrible with in depth microsoft networking. ok, ok i know that sounds pathetic, but it true. I have been working with (fighting with actually) DNS, WINS, and AD on my server. I dumped all of it, except for WINS, and set the network to a workgroup. and I have the router doing DHCP. Tell me, in order to get a remote office in the same workgroup, you must have two WINS servers? I have the remote office connected via ip. but in the workgroup, the remote office is not visable. i can ping the computers on the remote network, but not see them. Not to get off the discuss of Netbeui, but we have the same interests...what can I say.
brian
i understand now....it has become more of a microsoft situation!!! I confess, i am terrible with in depth microsoft networking. ok, ok i know that sounds pathetic, but it true. I have been working with (fighting with actually) DNS, WINS, and AD on my server. I dumped all of it, except for WINS, and set the network to a workgroup. and I have the router doing DHCP. Tell me, in order to get a remote office in the same workgroup, you must have two WINS servers? I have the remote office connected via ip. but in the workgroup, the remote office is not visable. i can ping the computers on the remote network, but not see them. Not to get off the discuss of Netbeui, but we have the same interests...what can I say.
brian
Dont feel bad.. Windows has several nasty surprises for the unsuspecting network engineer. One WINS server is needed. What is needed on the router, is a command called *IP HELPER* This command entered on the interfaces closet to the client/server allows the forwarding of 10 predetermined protocols like DHCP (ports UDP 67,68), TFTP, DNS(UDP port 53) and most importantly ports 137 and 138 (UDP) which is what WINS, browsing, logging into PDC needs and a few other services. FOr DHCP, only the client side needs the ip helper but for browsing, both the server and client side needs it since either can start the request for services sequence or start sending info like master browser lists and so on.
IF you are of the slightly more security minded, you can manually set each protocol you need to be forwarded instead of using IP helper as a global setting.
IP helper works by taking the broadcast packets (UDP 137/138) for example and "rewraps" them as a unicast IP packet. It then looks at the network target you have specified in the command and routes them to there. Once there, the last router will unwrap the packet coverting it back into a UDP packet BUT with the router as the requester. The server gets the UDP packet, reads it, supplies the requested service with the router as the target. The router gets the new packets and rewrites the header info to send it back to the host that wanted it. There is alot more that can happen depending on different configurations but you get the idea of how it works.
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
IF you are of the slightly more security minded, you can manually set each protocol you need to be forwarded instead of using IP helper as a global setting.
IP helper works by taking the broadcast packets (UDP 137/138) for example and "rewraps" them as a unicast IP packet. It then looks at the network target you have specified in the command and routes them to there. Once there, the last router will unwrap the packet coverting it back into a UDP packet BUT with the router as the requester. The server gets the UDP packet, reads it, supplies the requested service with the router as the target. The router gets the new packets and rewrites the header info to send it back to the host that wanted it. There is alot more that can happen depending on different configurations but you get the idea of how it works.
MikeS
Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
- Status