NetBIOS vs WinSock Applications

David Frick

unread,

Jun 28, 1998, 3:00:00 AM6/28/98

to

It is my understanding that applications that communicate over a network are
written to one of two APIs: NetBIOS or WinSOCK (Windows Sockets). I also
understand that Microsoft is transitioning away from NetBIOS to WinSOCK.

In the articles I've read on the differences between these two APIs, the
authors cite examples of applications built to either specification. For
example, they always site ftp and Telnet as WinSock applications and the
Microsoft NT logon and networking functions as examples of NetBIOS.

This may be a dumb question but where do general business applications fit
into the picture?

For example, would Excel be characterized as a NetBIOS application? Or does
it operate at a higher layer where the distinction between networking APIs
does not matter?

If NT 5 comes out and you want to run only WinSock, do you have to purchase
all new business applications?

I would be very grateful if anyone could enlighten me on this issue.

Thanks
Dave
--------
David R. Frick & Co., CPA
http://www.frick-cpa.com
da...@frick-cpa.com
7640...@compuserve.com

Greg Askew

unread,

Jun 28, 1998, 3:00:00 AM6/28/98

to

NetBIOS and Windows Sockets are generally referred to in the
context of name resolution (share names - printers, shared folders, server
names, domain names, etc). There are many fundamental system-level
functions that use NetBIOS that are transparent to user applications.

There are applications that actually used NetBIOS as a programming
API for network functions, but these are generally rare and very old DOS apps.

It may be worth noting you can use Windows sockets for many things now,
such as name resolution when mapping drives and printers over the Internet.
Exchange and SQL server also support Winsock client/server communications.
--
Greg Askew
g...@REMOVE-THISmindspring.com

John F. Moehrke

unread,

Jun 29, 1998, 3:00:00 AM6/29/98

to

David Frick wrote in message <#9vG8Qro...@uppssnewspub05.moswest.msn.net>...

>It is my understanding that applications that communicate over a network are
>written to one of two APIs: NetBIOS or WinSOCK (Windows Sockets). I also
>understand that Microsoft is transitioning away from NetBIOS to WinSOCK.
>
>In the articles I've read on the differences between these two APIs, the
>authors cite examples of applications built to either specification. For
>example, they always site ftp and Telnet as WinSock applications and the
>Microsoft NT logon and networking functions as examples of NetBIOS.
>
>This may be a dumb question but where do general business applications fit
>into the picture?

not a dumb question at all... The answer is not an easy one, and thus why
you didn't find the answer. The answer is either, or as you will see none...

>
>For example, would Excel be characterized as a NetBIOS application? Or does
>it operate at a higher layer where the distinction between networking APIs
>does not matter?

Excel doesn't interface to the network really. It uses the Filesystem. If the filesystem
is redirected across the network, then indirectly Excel looks like it is using the
network. But even here this is not an easy question, because Microsoft NT Network
(aka, SMB, Lan Man, etc...) uses Netbios... Network File System (NFS) uses
a low level api that is at the same level as WinSock......

>
>If NT 5 comes out and you want to run only WinSock, do you have to purchase
>all new business applications?

should not... As you see from above the "business apps" that you are referring
to may simply use a filesystem...