Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Sean Casey

Pages: 1 ... 5 6 [7] 8 9
91
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 19, 2019, 07:05:26 am »
No, it's not to remain mounted.  That was to check to see if you could access your Windows share using your Windows machine's loopback adapter. 

I primarily use Linux and rarely boot Windows.  The latest version of Windows I have is v.7 and I understand you are using v.10.   Assuming you have your OS/2 software configured correctly, it's possible you might also run into security negotiation issues with Windows.   

The following settings are to make your Windows security less restrictive and are applicable to Windows v.7 but could very well apply to your Windows 10 host.  This will weaken your Windows security, but will allow older clients, such as OS/2, access.    I have tested this using a Warp 4 client and NetDrive connecting to a Windows 7 share.

=============

1) Type secpol.msc at the Windows command prompt

Browse to "Local Policies" - "Security Options".  Look for "Network Security: LAN Manager authentication level" and open it.  Click on the menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated".  Apply the setting.

2) In the Advanced sharing settings page of Network and sharing center, you need to have it set as Work/Home profile.

-Enable network discovery
-Turn on file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers

3) Enter "gpedit.msc" at the Windows command prompt. Open "Computer Configuration"/Windows Settings/Security Settings/Local Policies/Security Settings.  In the right pane, enable the following policies:

-Enable network discovery
-Turn on  file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers




92
Applications / Re: DB/2 Version 2 CAE for Win16
« on: May 17, 2019, 04:43:49 pm »
Thank you very much .  I'll revisit how I installed Win32s v1.3 now that I know the v5.2 client should have worked with Win-OS2.

93
Applications / DB/2 Version 2 CAE for Win16
« on: May 15, 2019, 07:20:49 pm »
Hi,

Does anyone know where I can find a copy of the version 2 DB/2 CAE for Windows 3.1?  The file “win31cae.exe” was once on Hobbes, but has been removed.  I found a copy of the v.5.2 Win16 client, but receive a win32s 1.30 error when installing (I have 1.25/1.30 win32s installed.)

Thank you.

94
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 15, 2019, 04:26:36 am »
Hi Mauro,

Your networking and authentication look fine.  Your issue appears to involve how smbclient was installed as it is not able to see your network.  I can't think of anything else other than going back over your installation of smbclient.

Your NetDrive installation doesn't have much in the way of software dependencies other than meeting minimum patch levels for your OS.  The NetDrive installation (and smb plugin) for my newly installed vanilla Warp 4 client didn't require any manual configuration for the software's installation, and the set up of those few configuration screens.  There are manual installation instructions you might want to review to help verify your installation.   I would focus first on getting your NetDrive working before moving back to getting the smbclient package installed.

It's not uncommon for me to spend hours and sometimes days to resolve my OS/2 related issues. Keep at it and I'm confident you will eventually get it working.   I'm happy to share any information on my smbclient and NetDrive installation configurations if you need a working reference point.

95
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 10, 2019, 02:01:22 am »
What do you see when typing the following at an OS/2 command prompt:  smbtree -N

96
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 08, 2019, 02:08:09 am »
Hi,

I was fortunate to have had the Samba client preinstalled for me on ArcaOS.  My smb.conf is located at \mptn\etc\samba\smb.conf.   I suspect the location can vary based on how your installation was configured, but it's safe to assume smb.conf should be located in your samba directory as it always is in the *nix world.

By running smbtree -N you will validate if your client and server are translating correctly, otherwise your network map might show strange output/characters.   My codepage files are located under the smbclnt subdirectory \sys\apps\smbclnt\codepage\.

I have installed NetDrive on a Warp 4 client without needing to install the samba client, so you might want to put the client install on hold and see if you can get your NetDrive working.

97
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 02, 2019, 06:37:46 pm »
Networking looks good and that last error you posted points to an issue with your Samba client installation - your smb.conf file couldn't be found, which is needed by the client utilities.   

Per the following readme client installation guidance (smbclut-1_3_0-1054), see if your client is appropriately configured:

Manual installation for older systems:
======================================
The following 3 files should be placed into \lib directory below the
directory you created in step 1. Their purpose is to help with character
translation in certain utilities. Run smbtree.exe -N in order to find out
whether these table files are actually found or not.
   lib\lowcase.dat
   lib\upcase.dat
   lib\valid.dat
Put the enclosed smb.conf in %ETC%\samba. It's purpose is more or less to make
the utilities happy when they check for its presence. It is however recommended
to set the workgroup properly.
======================================

Unrelated to this smbclient issue, I'm not sure what direction to go for the NetDrive error you received.  See if you missed something in Arca Noae's NetDrive installation, checking against their manual installation instructions (https://www.arcanoae.com/shop/netdrive-for-os2/).


98
Applications / Re: Samba client on OS2 Warp 4.52
« on: May 02, 2019, 12:13:57 am »
From your OS/2 machine are you able to ping 192.168.56.1?

99
Applications / Re: Samba client on OS2 Warp 4.52
« on: April 29, 2019, 08:40:41 pm »
Hi Tom,

Windows should provide the netbios over TCP/IP output needed to obtain the hostname, IP address and workgroup as follows:

C:\Users\SVC>nbtstat -n
Local Area Connection:
Node IpAddress: [199.50.132.203] Scope Id: []

                NetBIOS Local Name Table
       Name               Type         Status
    ---------------------------------------------
    SATELLITE      <00>  UNIQUE      Registered
    SATELLITE      <20>  UNIQUE      Registered
    UNIVERSE       <00>  GROUP       Registered
    UNIVERSE       <1E>  GROUP       Registered

100
Applications / Re: Samba client on OS2 Warp 4.52
« on: April 29, 2019, 03:32:49 am »
I am assuming you are using Windows as your host machine and you are running OS/2 as a virtualized guest and would like your OS/2 guest to access your Windows file system using a Windows share. 

Use the smbclient -L command with your Windows IP address.  The 127.0.0.1 address you had used is your OS/2 "local" address, also called your loopback address.  To find your Windows IP address and your Windows workgroup, get to a command line on your Windows machine and type "nbtstat -n".  This is the address you should use when typing smbclient -L xxx.xxx.xxx.xxx at an OS/2 command prompt.  You will also see your workgroup name (identified as TYPE GROUP).

Before you try to access your Windows share from OS/2, you can test accessing your Windows share from within Windows itself.  Get to a Windows command line and type "net share" to identify the share you have created.  You will see hidden system shares with a dollar sign "$", but you should see the share you created without the dollar sign. 

Once you confirm you have created a Windows share and can see it with the Windows "net share" command, from the Windows command line,  create a mount point to your share to see that you can access the share from Windows.   You would do this by typing the following at a Windows command prompt:

"net use z: \\xxx.xxx.xxx.xxx\sharename persistent:yes"       

Replace "z:" with any unused drive letter you want to use as a mount point.  Replace "xxx.xxx.xxx.xxx" with your Windows machine's IP address obtained from the "nbtstat -n" command.   Replace "sharename" with the name of the share you created and confirmed existed with the "net share" command. 

If your share exists and you have permission to access the share, you should be able to change to the mount point (z:) and issue a "dir" command to see the contents of your share.

If this all works, then go back to OS/2 and use the command smbclient \\xxx.xxx.xxx.xxx\sharename using your Windows host IP address and Windows sharename.  You hopefully will connect to the share and have an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share as you had  done on your Windows machine.

While doing the above might seem like a PITA, it's helpful to diagnose where you might be having a problem.  If the above works, then you should be able to get NetDrive configured and working with the above IP address, workgroup and sharename.

101
Applications / Re: Samba client on OS2 Warp 4.52
« on: April 28, 2019, 06:10:30 pm »
Hi Mauro,

It would be helpful to confirm the shares you made available on your network.   At an OS/2 command line, type the following, replacing "xxx" with the IP or host name (if defined in your \mptn\etc\hosts file) of the host having the shares:

            smbclient -L xxx.xxx.xxx.xxx

If your are unable to enumarate your shares with the above command, you will need to verify your host machine has available shares. 

If the above returns a list of available shares, connect to one of the shares using the following OS/2 command, replacing "zzz" with your share name.  If you have user security established on your share, you will be prompted for a password.  If you need to identify a different user when connecting, add "-U username" to the following command to identify the user.

           smbclient \\xxx.xxx.xxx.xxx\zzz

If you successfully connect to the share, you will be at an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share.


102
Applications / Re: Samba client on OS2 Warp 4.52
« on: April 26, 2019, 03:55:02 am »
Hi,

You will also need to install the smb NetDrive plugin.   You can find it here: http://trac.netlabs.org/samba

Once installed, use the NetDrive Volume menu and select "Attach New Volume" menu option.  You will then elect a drive letter to assign your mount point.

With your mount point highlighted within NetDrive, select the Resource menu and the "Mount Resource" menu option. You will be presented with a screen where you should see the option of "smbfs" which is your samba plugin you installed.   

Clicking the "Properties" button will present a screen where you identify your smb workgroup, server, share name, and login credentials.  Once you complete these entries and click the Done button, you will then have your mount point defined and it should be mounted and ready for use.

To save these settings for future use, select the NetDrive menu and the Volume Configuration Save option. 

If you ever lose your mount point due to network issues, you can restart NetDrive by selecting the NetDrive menu, and Control Program Start option.


103
Applications / Re: XFree86-OS/2
« on: March 28, 2019, 01:00:26 am »
For the moment I can only launch the X11 full screen session, but I don't understand how to run X11 apps on windowed mode, like Doug and Sean are showing on their screenshots.

Unlike the commercial X desktops like Exceed and PMX, XFree was designed to run full screen and not operate in a seamless windowed mode, nor does it share the Clipboard w. OS/2.  However, you should be able to switch between XFree and PM using Alt-Escape. 

Unfortunately for my use, PMX is too sluggish.  Since my OS/2 desktop is run within a Linux VM, I'll just have to minimize OS/2 to access the few Linux applications I have been unable to replace with native PM alternatives.   I have an Exceed license I formerly used w. Windblows and the performance was fine, so I'll need to revisit why PMX is so sluggish with OS/2.

104
Applications / Re: XFree86-OS/2
« on: March 27, 2019, 03:29:58 am »
Hi Martin,

Doug and I were successful using PMX.  There wasn't anything unusual about my installation/configuration.  Have you considered giving this a try?   

105
Applications / Re: XFree86-OS/2
« on: March 25, 2019, 05:15:45 pm »
Installed PMX and Alex Taylor's OpenSSH.  Screen updates are extremely slow and menus aren't very legible   I'll need to tinker to see if this can be improved.

Pages: 1 ... 5 6 [7] 8 9