--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3H00007 Date: 03/10/98 From: JONATHAN DE BOYNE POLLARD Time: 10:06am \/To: JOHAN ZWIEKHORST (Read 2 times) Subj: NT Client for OS/2 JZ> OS/2 Warp 3 Connect and OS/2 Warp 4 will work fine, provides the NT JZ> server uses NetBEUI. If the server is using IPX or TCP/IP without JZ> NetBIOS, you can't connect to it with OS/2 clients [...] OS/2 Warp 3 Connect and OS/2 Warp 4 have the Netware Requester. If the Netware Requester cannot connect to an IPX-based server, then the blame should lie with the IPX server, since the Netware Requester for OS/2 *can* connect to real Netware Servers quite happily. JdeBP --- FleetStreet 1.19 NR * Origin: JdeBP's point, using Squish (2:440/4.3) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3H00008 Date: 03/12/98 From: JOHAN ZWIEKHORST Time: 08:52pm \/To: NEIL CROFT (Read 2 times) Subj: NT Client for OS/2 Hi Neil! In your message to me, dated , you wrote: JZ>> OS/2 Warp 3 Connect and OS/2 Warp 4 will work fine, provides the JZ>> NT server uses NetBEUI. If the server is using IPX or TCP/IP JZ>> without >NC: It doesn't. I can guarantee that 'cos it's coming through an IP only >NC: firewall that I manage. =o) JZ>> NetBIOS, you can't connect to it with OS/2 clients (although you JZ>> can with NT Workstation and Win95). Basically, if Windows for JZ>> Workgroups can connect to it, so can OS/2. >NC: Time to play with the netbios over IP methinks. Yes, that will work. I've tried it myself and an OS/2 client will recognize and connect to an NT server with NetBIOS over TCP/IP. It does mean a network performance penalty, however. ._|~/_ johanzw@club.innet.be http://www.club.innet.be/~year1355/ --- Maximus-CBCS v3.01 * Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3I00000 Date: 03/12/98 From: SCOTT LITTLE Time: 10:16pm \/To: LEE ARONER (Read 2 times) Subj: Protocols? [ Quoting LEE ARONER to SCOTT LITTLE ] LA> BTW, you don't NEED NetB to share. You can use just IP, or IPX. LA> NetBeui is just a proprietary extension of NetBios by MS. The IBM LA> NetBios is actually more capable, and is completely compatible LA> with the MS version. Thanks, I fixed it. I spent about 40 minutes on the 3COM site (which is a long time at 4Mb) and found the fixes. I also installed NetBIOS as you say rather than NetBIOS over TCP/IP. Works. The problem now is the sharing. How do I disable all the access profiles and such (if I wanted OS/2 Server I would have BOUGHT it). All I need to do is share a directory, and have everything underneath automatically available - at the moment I have to "Update Share" to apply permissions to directories below the share. This is a pain in the butt for CDROMs, as I have to update the share every time I change a CD. -- Scott Little, 3:712/848@fidonet ; admin@cyberia.asstdc.com.au www.asstdc.com.au/~cyberia --- FMail/Win32 1.22 * Origin: Cyberia: You know you want it. [02-9534-1702] (3:712/848) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3I00001 Date: 03/13/98 From: JEFF DUNLOP Time: 06:05pm \/To: JONATHAN DE BOYNE POLLARD (Read 2 times) Subj: NT Client for OS/2 JZ>> OS/2 Warp 3 Connect and OS/2 Warp 4 will work fine, provides the NT JZ>> server uses NetBEUI. If the server is using IPX or TCP/IP without JZ>> NetBIOS, you can't connect to it with OS/2 clients [...] JdBP> OS/2 Warp 3 Connect and OS/2 Warp 4 have the Netware Requester. If he JdBP> Netware Requester cannot connect to an IPX-based server, then the lame JdBP> should lie with the IPX server, since the Netware Requester for OS/2 JdBP> *can* connect to real Netware Servers quite happily. He is referring to NT and W95 servers running over the IPX protocol. Jeff --- GoldED/2 2.42.G0615 * Origin: DB/Soft Online - Sacramento, CA (916)927-2349 (1:203/16) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3I00002 Date: 03/13/98 From: FRANK SEXTON Time: 08:42pm \/To: SCOTT LITTLE (Read 2 times) Subj: Protocols? -=> /* Quoting Scott Little to LEE ARONER */ <=- SL> The problem now is the sharing. How do I disable all SL> the access profiles and such (if I wanted OS/2 Server SL> I would have BOUGHT it). All I need to do is share a SL> directory, and have everything underneath SL> automatically available - at the moment I have to SL> "Update Share" to apply permissions to directories SL> below the share. This is a pain in the butt for SL> CDROMs, as I have to update the share every time I SL> change a CD. Try this... First delete your current share. Then recreate it as "C:\directory\" or "F:\directory\" or whatever. Then, (to the best of my memory) when asked if you want to apply the ACL control click on CANCEL (or NO). On my system this results in the entire drive and all subdirectories being shared. -Frank (fsexton@ibm.net - http://www.concentric.net/~fsexton) --- Blue Wave/OS2 v2.30 * Origin: Wildcard BBS - Thornton, CO 1-303-252-0491 (1:104/725) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3I00003 Date: 03/13/98 From: WILL HONEA Time: 02:11pm \/To: JONATHAN DE BOYNE POLLAR (Read 2 times) Subj: about connect with two o Jonathan de Boyne Pollard wrote to Thomas W. Mueller on 03-03-1998 JP> JdB>> (2) Start the requester when you boot. Do this by creating a JP> JdB>> shadow of the "Start File and Print Client" object in your Startup JP> JdB>> folder. JP> JP> TWM> The problem with that is, that it takes ages to start. Since Warp 4 JP> TWM> takes a lot of time to boot anyway, it is possible to just start he JP> TWM> requester from the config.sys: run=c:\ibmlan\netprog\net.exe start JP> TWM> req In fact, there are several APARs addressing race conditions which will lock the machine due to sequenceing problems during initialization of the requester and TCP/IP code. At last check, they have gone to a semaphore file in a effort to syncronize the contending sessions, so the timing and sequence are improtant. JP> I wouldn't recommend using RUN= in CONFIG.SYS for this purpose. JP> There are session management issues that affect processes started JP> from CONFIG.SYS. If you want to start the Requester earlier than JP> the processing of the desktop Startup folder, then I'd suggest JP> using \STARTUP.CMD . JP> JP> ( Which is, in fact, where earlier versions of IBM LAN JP> Requester used to install themselves. ) JP> JP> > JdeBP < Will Honea --- Maximus/2 2.02 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3I00004 Date: 03/13/98 From: WILL HONEA Time: 02:16pm \/To: SCOTT LITTLE (Read 2 times) Subj: Protocols? Scott Little wrote to LEE ARONER on 03-12-1998 SL> The problem now is the sharing. How do I disable all the access SL> profiles and such (if I wanted OS/2 Server I would have BOUGHT it). SL> All I need to do is share a directory, and have everything SL> underneath automatically available - at the moment I have to "Update SL> Share" to apply permissions to directories below the share. This is SL> a pain in the butt for CDROMs, as I have to update the share every SL> time I change a CD. Something is screwy here. With Warp Connect and Warp 4, I've never seen this! I change CD's all the time and never run into a problem. As a suggestion, try sharing the drive a x: rather than x:\ - I seem to recall that the 2 specifications work differently. Just checked - my shared resource is defined as x:\ and all subdirectories are available on the other machines after changing CDs. Will Honea --- Maximus/2 2.02 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3J00000 Date: 03/14/98 From: JEFF DUNLOP Time: 04:05am \/To: FRANK SEXTON (Read 2 times) Subj: Protocols? SL>> The problem now is the sharing. How do I disable all SL>> the access profiles and such (if I wanted OS/2 Server SL>> I would have BOUGHT it). All I need to do is share a SL>> directory, and have everything underneath SL>> automatically available - at the moment I have to SL>> "Update Share" to apply permissions to directories SL>> below the share. This is a pain in the butt for SL>> CDROMs, as I have to update the share every time I SL>> change a CD. FS> Try this... FS> First delete your current share. Then recreate it as FS> "C:\directory\" or "F:\directory\" or whatever. Then, (to FS> the best of my memory) when asked if you want to apply the FS> ACL control click on CANCEL (or NO). On my system this FS> results in the entire drive and all subdirectories being FS> shared. For CDs, you really want to share the drive instead of sharing the root directory of a drive. Here are the steps. The ACL management varies slightly between Warp Server and Connect, but the end result is the same. - Create the resource name. Do NOT allow the ACL to be created. Select cancel instead. - Go to the Drive icon, RMB. Select Manage Access. - The drive is listed as a shared drive. Add your members and give them permissions. Jeff --- GoldED/2 2.42.G0615 * Origin: DB/Soft Online - Sacramento, CA (916)927-2349 (1:203/16) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3J00001 Date: 03/11/98 From: TONY LANGDON Time: 09:47am \/To: MARK LEWIS (Read 2 times) Subj: socket serving It's 03 Mar 98 19:59:58, We'll return to mark lewis and Mike Ruskai's discussion of socket serving ml> if your 172.16 address above is part of the 3rd range i'm thinking of, ml> please ignore this message and pass the salt ;-) Those addresses are the third range, reserved for isolated networks. :-) 172.16.0.0 - 172.31.x.x ... Nothing is lost... where everything remains. --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F3K00000 Date: 03/13/98 From: LEE ARONER Time: 09:33pm \/To: SCOTT LITTLE (Read 2 times) Subj: Protocols? LA> BTW, you don't NEED NetB to share. You can use just IP, or IPX. LA> NetBeui is just a proprietary extension of NetBios by MS. The IBM LA> NetBios is actually more capable, and is completely compatible LA> with the MS version. SL> Thanks, I fixed it. I spent about 40 minutes on the 3COM site (which is a > long time at 4Mb) and found the fixes. I also installed NetBIOS as you ay > rather than NetBIOS over TCP/IP. Works. You'd only need the NetB over IP if you needed to pass NetB through a router, or for connecting to a server that doesn't directly support NetB, such as a Samba box. SL> The problem now is the sharing. How do I disable all the access profiles and > such (if I wanted OS/2 Server I would have BOUGHT it). All I need to do s > share a directory, and have everything underneath automatically available - > at the moment I have to "Update Share" to apply permissions to irectories > below the share. This is a pain in the butt for CDROMs, as I have to update > the share every time I change a CD. The trick with a CD is you don't create an access profile from the file and print manager. You create the share, then click "Cancel" when the "Create Access Profile" thing comes up. Then close the manager and open your drives folder. select "Manage Access" from the drive (CD) right click menu, hit "OK" at the "Create Access Control Profile" prompt, add the groups and users you want to have access, hit "Add" and "OK" and you're done...remote users will have access to the entire drive regardless of the disk in the tray. I believe you can also create the share directly from the Drives menu, although I've never done it that way...habit. LRA -- SPEED 2.00 #2720: Fortunately, I had a backup dated 1/1/80 --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Memory Alpha - (253) 859-6200 (1:343/311)