Thoughts...

Post #53,592 by Simon_Jester 9/27/02 3:44:28 PM 9/27/02 3:55:28 PM Reply	Thoughts... I didn't think the WINS gave out ip addresses, but I'm definitely not up to speed on WINS. In any case, - if you have DHCP, allow the DHCP to assign the IP address to the linux box. Get the IP address of the Linux box (ping something) and you can then scp stuff to it and back. If you can, a static ip is better in my mind - especially as you can get the admin to firewall that IP off so that no one from the outside can see that box. (But it may require permission of getting an IP address.) SAMBA is an option - but it's a small amount of work to set it up. (But then you have access to printers and everything else. ;-) ) SMBclient is strictly a client service, you don't even need to use DNS. (smbclient -L I think to list shares). (It's okay, but I like scp better.) Actually, if you're sharing the Win2000 box, you can mount the drives on your Linux box (without starting SAMBA service on your linux box iirc). Edited by Simon_Jester Sept. 27, 2002, 03:55:28 PM EDT Thoughts... I didn't think the WINS gave out ip addresses, but I'm definitely not up to speed on WINS. In any case, - if you have DHCP, allow the DHCP to assign the IP address to the linux box. Get the IP address of the Linux box (ping something) and you can then scp stuff to it and back. If you can, a static ip is better in my mind - especially as you can get the admin to firewall that IP off so that no one from the outside can see that box. (But it may require permission of getting an IP address.) SAMBA is an option - but it's a small amount of work to set it up. (But then you have access to printers and everything else. ;-) ) Collapse All History
Post #53,593 by deSitter 9/27/02 3:56:47 PM Reply	WINS In 1 Minute NetBIOS is not routable, but you can encapsulate it in TCP/IP. In order to run LAN Manager on pure TCP/IP, you need a way to resolve NetBIOS names into IP addresses, and that is what WINS does. It's strictly an adhoc solution to the problem of having a NOS that was not written with routing in mind work with a routable protocol. Also, NetBIOS was LOUD (based on broadcasts) so you need a way of things getting seen without always having to announce themselves. The chattiness of NetBIOS is not an issue on a small network, but imagine 10000 clients constantly broadcasting. IOW, LAN Manager was a simple NOS created in the infancy of PC nets that lived far longer than it needed to. -drl
Post #53,659 by pwhysall 9/28/02 2:24:02 AM Reply	NetBIOS /is/ routable. It's a higher-level protocol that can use any transport including IPX/SPX and TCP/IP. It's NetBEUI that isn't routable. Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #53,779 by deSitter 9/29/02 12:02:43 AM Reply	Re: NetBIOS /is/ routable. NetBIOS is to NetBEUI as TCP is to IP, as transport is to network (protocol), so you are correct to make the distinction, but NetBIOS/NetBEUI is never routable because there is no room in the packet for addresses - that's why it uses broadcasting, as opposed to TCP/IP, which uses multicasting. Multicasting relies on a list of addresses which can be compared at the hardware level, while broadcasting relies on the operating system to decide what to do with a packet. So broadcast packets are not targeted, that is, there is no address information in them, while multicast packets contain address information that can be compared against a list held by the NIC hardware. -drl
Post #53,785 by pwhysall 9/29/02 1:50:02 AM Reply	Er, no. TCP/IP uses broadcasts - simply send your packet to x.x.x.255, for a Class C example. We route NetBIOS across distinct networks to enable NT4 boxes to participate in SMB browsing. The only caveat is that you must disable the Computer Browser service on the box doing the routing, or else use a dedicated router. (The reason being that on a multihomed box, if the Browser service is running, it won't propagate NetBIOS browse traffic across interfaces.) Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #53,817 by deSitter 9/29/02 10:29:33 AM Reply	Re: Er, no. Well, it's terminology at some point - the key issue is address information in a packet. Are you saying you have a separate NetBIOS protocol installed on some machines, or some all NetBIOS programs? If so then the routers are intelligently converting it to NBT or something like that and sending that among themselves. There's extra information supplied by the router. This is no different in principle than using NBT on the client. -drl

Welcome to IWETHEY!