I'm trying to understand the client and server communication. But I have run into some terms which I need some help to understand:
1. Named Pipes over NetBIOS
2. Named Pipes over NetBEUI
3. Named Pipes over TCP/IP
4. NetBIOS over TCP/IP
5. SMB over NetBios
6. SMB over NetBEUI
7. SMB over TCP/IP
8. RPC over NetBIOS
9. RPC over NetBEUI
10. RPC over TCP/IP
I have a feeling that #1 and #5 actually means the same thing. Also, #3 and #7 means the same thing.
Is the following the correct order of the communication path?
Named Pipes
SMB
NetBIOS
TCP/IP or NetBEUI
I have the following understanding:
1. Named Pipes is a network library.
2. TCP/IP and NetBEUI are network transport protocols.
You have many things mixed together that are fundamentally different.
This can't easily be explained. I think your point is which ports must
be enabled based on what services are being used, as opposed to just
being active and unused. This is difficult to answer without alot of
experimentation and understanding of the interdependance of services.
I understood named pipes to be an app to app info exchange by files.
Named pipes can operate over TCP/IP, but are verbose and performance
becomes degraded over slow networks.
RPC stands for remote procedure call. These are transmitted over
TCP/IP RPC are means by whihc applications communicate and are at
least a level above TCP/IP..
SMB is also referred to as Samba - means of Windows and Linux file
sharing, and is again at a higher level than TCP/IP.
NetBios is a protocol that I understood was native to Novel networks,
and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
On Tue, 29 Jun 2004 13:03:02 -0700, "=?Utf-8?B?cGV0ZXI=?="
<peter@.discussions.microsoft.com> wrote:
>I'm trying to understand the client and server communication. But I have run into some terms which I need some help to understand:
>1. Named Pipes over NetBIOS
>2. Named Pipes over NetBEUI
>3. Named Pipes over TCP/IP
>4. NetBIOS over TCP/IP
>5. SMB over NetBios
>6. SMB over NetBEUI
>7. SMB over TCP/IP
>8. RPC over NetBIOS
>9. RPC over NetBEUI
>10. RPC over TCP/IP
>I have a feeling that #1 and #5 actually means the same thing. Also, #3 and #7 means the same thing.
>Is the following the correct order of the communication path?
>Named Pipes
>SMB
>NetBIOS
>TCP/IP or NetBEUI
>I have the following understanding:
>1. Named Pipes is a network library.
>2. TCP/IP and NetBEUI are network transport protocols.
>
|||Hi Lou,
Thank you for the explanation.
Are the followings correct?
1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS, #5 SMB over NetBios, and #6 SMB over NetBEUI.
3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 SMB over NetBios, and #7 SMB over TCP/IP.
Thank you for your help,
Peter
"Lou Arnold" wrote:
> You have many things mixed together that are fundamentally different.
> This can't easily be explained. I think your point is which ports must
> be enabled based on what services are being used, as opposed to just
> being active and unused. This is difficult to answer without alot of
> experimentation and understanding of the interdependance of services.
> I understood named pipes to be an app to app info exchange by files.
> Named pipes can operate over TCP/IP, but are verbose and performance
> becomes degraded over slow networks.
> RPC stands for remote procedure call. These are transmitted over
> TCP/IP RPC are means by whihc applications communicate and are at
> least a level above TCP/IP..
> SMB is also referred to as Samba - means of Windows and Linux file
> sharing, and is again at a higher level than TCP/IP.
> NetBios is a protocol that I understood was native to Novel networks,
> and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
> On Tue, 29 Jun 2004 13:03:02 -0700, "=?Utf-8?B?cGV0ZXI=?="
> <peter@.discussions.microsoft.com> wrote:
>
>
|||Sorry, i realy don't have enough experience to answer your questions
and I'm not sure anyone can in this forum. You'l need to browse the
internet or ask in networking groups.
On Wed, 30 Jun 2004 01:05:01 -0700, "=?Utf-8?B?UGV0ZXI=?="
<Peter@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Lou,
>Thank you for the explanation.
>Are the followings correct?
>1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
>2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS, #5 SMB over NetBios, and #6 SMB over NetBEUI.
>3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 SMB over NetBios, and #7 SMB over TCP/IP.
>Thank you for your help,
>Peter
>
>"Lou Arnold" wrote:
|||Lou,
Thank you for your help. I understand these questions are kind of beyond the scope of SQL Server.
Peter
"Lou Arnold" wrote:
> Sorry, i realy don't have enough experience to answer your questions
> and I'm not sure anyone can in this forum. You'l need to browse the
> internet or ask in networking groups.
>
> On Wed, 30 Jun 2004 01:05:01 -0700, "=?Utf-8?B?UGV0ZXI=?="
> <Peter@.discussions.microsoft.com> wrote:
>
>
Friday, February 24, 2012
Communciation between MS SQL Server and client
Labels:
client,
communciation,
communication,
database,
microsoft,
mysql,
named,
oracle,
pipes,
run,
server,
sql,
terms,
understand1
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment