NetWare Core Protocol over TCP [7:26131]
I am interested to know how many people use NetWare Core Protocol (NCP) over TCP. Like Howard, I didn't think this was the normal way of handling a migration from IPX to IP, although it certainly makes sense. So, a survey: can people on the list let us know if they use this? Note: I'm not criticizing Kevin, just gathering information. Regarding PEP, I did some research too. I couldn't find any proof that the transport-like part of NCP was based on PEP, which I thought disappeared, but it does make sense. The service provided by PEP is essentially the same as the service that NCP provides in its integrated transport level, to use Howard's great terminology. I would love to get a Sniffer trace of NCP over TCP. I have a rather old version of Sniffer but a brand new version of EtherPeek. Also I know NCP really well so I might recognize some stuff even if the decoder doesn't. The packet you sent before is just the TCP SYN. Do you have something later in the session with some NCP data? Could you send me (not the list) an attachment of a cleaned up trace file? I'll acknowledge you in my new book! ;-) THANKS. Priscilla At 12:26 AM 11/13/01, [EMAIL PROTECTED] wrote: 5.0 with an unmanageably large number of service pack applications. I believe the NWIP encapsulation as a preferred means of exchanging packets idea was buried with version 4. NW 5 servers may be installed with support for either or both protocol stacks. There exist various modules centering around the acronym cmd which allegedly facilitate hybrid environments slated to migrate to ip only. It's possible that servers thus configured encapsulate ipx within ip, but I'm far too undermotivated to ascertain the validity of that guess. I suppose that Novell has been fairly successful at obscuring the original meaning of PEP: many hits on general web searches turn up some documents on programmatically generating sending ipx packets in the name of fine-tuing network diagnostic tools such as DOOM. Seaching Novell leads you to conclude that it refers to their Professional Education Program. Howard C. Berkowitz @groupstudy.com on 11/12/2001 06:22:40 PM Please respond to Howard C. Berkowitz Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Kevin Cullimore) Subject: RE: What frame format used by TCP/IP? [7:25924] In contrast to the IPX-based implementation described below, packet captures seem to reveal that NCP DOES rely on a transport layer when using IP as a network layer mechanism. What version of NetWare? It's my understanding that 5.x is native TCP/IP with encapsulated IPX available for backwards compatibility. Incidentally, older IPX-based NCP had an integrated transport function, not SPX but something called PEP. Flags:0x00 Status: 0x00 Packet Length:66 Timestamp:19:09:38.677828 03/12/2001 Ethernet Header Destination: 00:90:7F:0F:0B:D5 Source: 00:10:A4:F5:5A:66 Protocol Type:0x0800 IP IP Header - Internet Protocol Datagram Version: 4 Header Length:5 (20 bytes) Precedence: 0 Type of Service: % Unused: %0 Total Length: 48 Identifier: 14671 Fragmentation Flags: %010 Do Not Fragment Fragment Offset: 0 (0 bytes) Time To Live: 128 IP Type: 0x06 TCP Header Checksum: 0xF3B3 Source IP Address:210.225.86.53 Dest. IP Address: xxx.xxx.xxx.x xxx.xx.xx.xxx No Internet Datagram Options TCP - Transport Control Protocol Source Port: 2583 Destination Port: 524 NCP Sequence Number: 1273813107 Ack Number: 0 Offset: 7 Reserved: %00 Code: %10 Synch Sequence Window: 16384 Checksum: 0x44D7 Urgent Pointer: 0 TCP Options: Option Type:2 Maximum Segment Size Length: 4 MSS:1460 Option Type:1 No Operation Option Type:1 No Operation Option Type:4 Length: 2 Opt Value: TCP Data Area:No more data. Frame Check Sequence: 0x04007C00 Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=26131t=26131 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: NetWare Core Protocol over TCP [7:26131]
Finally something I know a little bit about. NWIP is dead (thank the Novell gods). NCP runs natively over TCP now. When installing a Netware 5.1 server TCP/IP is now the default protocol. If you want to migrate from IPX to IP you do it by having a NetWare 5.x server serving as a IPX/IP gateway. It works very well. I've seen this in several environments especially new installations. In new installations there is very little reason to run IPX on your NetWare box at all. Now time to return to that switching book. Keith Townsend MCSE, CNE, CCNA http://townsendconsulting.com Priscilla Oppenheimer wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... I am interested to know how many people use NetWare Core Protocol (NCP) over TCP. Like Howard, I didn't think this was the normal way of handling a migration from IPX to IP, although it certainly makes sense. So, a survey: can people on the list let us know if they use this? Note: I'm not criticizing Kevin, just gathering information. Regarding PEP, I did some research too. I couldn't find any proof that the transport-like part of NCP was based on PEP, which I thought disappeared, but it does make sense. The service provided by PEP is essentially the same as the service that NCP provides in its integrated transport level, to use Howard's great terminology. I would love to get a Sniffer trace of NCP over TCP. I have a rather old version of Sniffer but a brand new version of EtherPeek. Also I know NCP really well so I might recognize some stuff even if the decoder doesn't. The packet you sent before is just the TCP SYN. Do you have something later in the session with some NCP data? Could you send me (not the list) an attachment of a cleaned up trace file? I'll acknowledge you in my new book! ;-) THANKS. Priscilla At 12:26 AM 11/13/01, [EMAIL PROTECTED] wrote: 5.0 with an unmanageably large number of service pack applications. I believe the NWIP encapsulation as a preferred means of exchanging packets idea was buried with version 4. NW 5 servers may be installed with support for either or both protocol stacks. There exist various modules centering around the acronym cmd which allegedly facilitate hybrid environments slated to migrate to ip only. It's possible that servers thus configured encapsulate ipx within ip, but I'm far too undermotivated to ascertain the validity of that guess. I suppose that Novell has been fairly successful at obscuring the original meaning of PEP: many hits on general web searches turn up some documents on programmatically generating sending ipx packets in the name of fine-tuing network diagnostic tools such as DOOM. Seaching Novell leads you to conclude that it refers to their Professional Education Program. Howard C. Berkowitz @groupstudy.com on 11/12/2001 06:22:40 PM Please respond to Howard C. Berkowitz Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Kevin Cullimore) Subject: RE: What frame format used by TCP/IP? [7:25924] In contrast to the IPX-based implementation described below, packet captures seem to reveal that NCP DOES rely on a transport layer when using IP as a network layer mechanism. What version of NetWare? It's my understanding that 5.x is native TCP/IP with encapsulated IPX available for backwards compatibility. Incidentally, older IPX-based NCP had an integrated transport function, not SPX but something called PEP. Flags:0x00 Status: 0x00 Packet Length:66 Timestamp:19:09:38.677828 03/12/2001 Ethernet Header Destination: 00:90:7F:0F:0B:D5 Source: 00:10:A4:F5:5A:66 Protocol Type:0x0800 IP IP Header - Internet Protocol Datagram Version: 4 Header Length:5 (20 bytes) Precedence: 0 Type of Service: % Unused: %0 Total Length: 48 Identifier: 14671 Fragmentation Flags: %010 Do Not Fragment Fragment Offset: 0 (0 bytes) Time To Live: 128 IP Type: 0x06 TCP Header Checksum: 0xF3B3 Source IP Address:210.225.86.53 Dest. IP Address: xxx.xxx.xxx.x xxx.xx.xx.xxx No Internet Datagram Options TCP - Transport Control Protocol Source Port: 2583 Destination Port: 524 NCP Sequence Number: 1273813107 Ack Number: 0 Offset: 7 Reserved: %00 Code: %10 Synch Sequence Window: 16384 Checksum: 0x44D7 Urgent Pointer: 0 TCP Options: Option Type:2 Maximum Segment Size Length: 4 MSS:1460 Option Type:1 No Operation Option Type:1 No Operation Option Type:4 Length: 2 Opt Value: TCP Data Area:No more data. Frame Check
RE: NetWare Core Protocol over TCP [7:26131]
A customer of mine is preparing for a conversion from Netware IPX to IP only. Total network is 350+ servers. 98% are Netware 5.1. On Netware 5.1, when 2 servers can communicate through IP they will use IP for all communications. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Priscilla Oppenheimer Sent: Tuesday, November 13, 2001 1:07 PM To: [EMAIL PROTECTED] Subject: NetWare Core Protocol over TCP [7:26131] I am interested to know how many people use NetWare Core Protocol (NCP) over TCP. Like Howard, I didn't think this was the normal way of handling a migration from IPX to IP, although it certainly makes sense. So, a survey: can people on the list let us know if they use this? Note: I'm not criticizing Kevin, just gathering information. Regarding PEP, I did some research too. I couldn't find any proof that the transport-like part of NCP was based on PEP, which I thought disappeared, but it does make sense. The service provided by PEP is essentially the same as the service that NCP provides in its integrated transport level, to use Howard's great terminology. I would love to get a Sniffer trace of NCP over TCP. I have a rather old version of Sniffer but a brand new version of EtherPeek. Also I know NCP really well so I might recognize some stuff even if the decoder doesn't. The packet you sent before is just the TCP SYN. Do you have something later in the session with some NCP data? Could you send me (not the list) an attachment of a cleaned up trace file? I'll acknowledge you in my new book! ;-) THANKS. Priscilla At 12:26 AM 11/13/01, [EMAIL PROTECTED] wrote: 5.0 with an unmanageably large number of service pack applications. I believe the NWIP encapsulation as a preferred means of exchanging packets idea was buried with version 4. NW 5 servers may be installed with support for either or both protocol stacks. There exist various modules centering around the acronym cmd which allegedly facilitate hybrid environments slated to migrate to ip only. It's possible that servers thus configured encapsulate ipx within ip, but I'm far too undermotivated to ascertain the validity of that guess. I suppose that Novell has been fairly successful at obscuring the original meaning of PEP: many hits on general web searches turn up some documents on programmatically generating sending ipx packets in the name of fine-tuing network diagnostic tools such as DOOM. Seaching Novell leads you to conclude that it refers to their Professional Education Program. Howard C. Berkowitz @groupstudy.com on 11/12/2001 06:22:40 PM Please respond to Howard C. Berkowitz Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Kevin Cullimore) Subject: RE: What frame format used by TCP/IP? [7:25924] In contrast to the IPX-based implementation described below, packet captures seem to reveal that NCP DOES rely on a transport layer when using IP as a network layer mechanism. What version of NetWare? It's my understanding that 5.x is native TCP/IP with encapsulated IPX available for backwards compatibility. Incidentally, older IPX-based NCP had an integrated transport function, not SPX but something called PEP. Flags:0x00 Status: 0x00 Packet Length:66 Timestamp:19:09:38.677828 03/12/2001 Ethernet Header Destination: 00:90:7F:0F:0B:D5 Source: 00:10:A4:F5:5A:66 Protocol Type:0x0800 IP IP Header - Internet Protocol Datagram Version: 4 Header Length:5 (20 bytes) Precedence: 0 Type of Service: % Unused: %0 Total Length: 48 Identifier: 14671 Fragmentation Flags: %010 Do Not Fragment Fragment Offset: 0 (0 bytes) Time To Live: 128 IP Type: 0x06 TCP Header Checksum: 0xF3B3 Source IP Address:210.225.86.53 Dest. IP Address: xxx.xxx.xxx.x xxx.xx.xx.xxx No Internet Datagram Options TCP - Transport Control Protocol Source Port: 2583 Destination Port: 524 NCP Sequence Number: 1273813107 Ack Number: 0 Offset: 7 Reserved: %00 Code: %10 Synch Sequence Window: 16384 Checksum: 0x44D7 Urgent Pointer: 0 TCP Options: Option Type:2 Maximum Segment Size Length: 4 MSS:1460 Option Type:1 No Operation Option Type:1 No Operation Option Type:4 Length: 2 Opt Value: TCP Data Area:No more data. Frame Check Sequence: 0x04007C00 Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=26145t=26131 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report
