OS/2, eCS & ArcaOS - Technical > Setup & Installation

Networking eCS & Win 7 new article !

(1/2) > >>

Greggory Shaw:
I need some help and comments for this !

I got the eCS to Win7 almost done and starting on the Samba server or Win 7 to eCS now.

http://os2notes.duckdns.org/os2win.html


Cheers,

Greggory

Neil Waldhauer:
I can't get the eCS EVFS-based SAMBA to connect at boot time. It will connect later, but I can't connect automatically. Any idea how to do this?

Greggory Shaw:

--- Quote from: Neil Waldhauer on August 22, 2015, 08:50:03 pm ---I can't get the eCS EVFS-based SAMBA to connect at boot time. It will connect later, but I can't connect automatically. Any idea how to do this?

--- End quote ---

I had something like that, then I installed the Samba server 12.wpi and then could see other computers in client EVFS.

There are so many different problems - also sometimes it's take minutes for changes to take affect.

After more testing this upgrade seems to be a hit or miss over all :( and really pissing me off ! On a new eCs install it worked, my production install failed, another new install failed, then work, SMH. However, installing Samba server below seem to fix everything.

Samba server:

ftp://os2user@os2notes.duckdns.org/

Password: os2

After installing Samba 1.2.wpi server install updates:

1) ftp://ftp.netlabs.org/pub/samba/server/test/samba-3.5.21-1.2.0-20130911.zip
2) ftp://ftp.netlabs.org/pub/samba/server/guitools/smbmon-25RC8-20150113-test.zip

After updating smbmon-25RC8-20150113-test.zip or Samba Status Monitor check the tab TDB files to see if all for correct and the server is working correctly (see attached pic).

And finally I messed things up so bad I had to uninstall everything and use the three wpi from the DVD to re-install everything. So you can start over too, use this way if you don't have backups of your system drive. You may get an error starting the EVFS client after a re-install, just update the client to evfsgui-25RC7-20141213.zip to fix that (evfsgui-25RC7 may overwrite your lmhosts file).

NOTE: if your tmp directories are on a RAM drive the install for Samba server will fail.

Could everyone post want their setup is for everyone please !


Greggory

Neil Waldhauer:
So it looks like you are installing the older 3.5 server rather than the newer 3.3 server.

On either, I think it's a good idea to check on how attributes and timestamps work before committing to a production environment. The 3.3 server has been tweaked to where I can use it. I know there has been work on KLibC to try to make permissions, timestamps, ownership and groups work. But OS/2 is not the same as Linux, so be careful.

On my production server, I have scripts to restore a lot of key files from backup after an bad client connects.

Installation of 3.3 always crashes at the end when creating the admin user. Users and Groups always crashes in the same place. I use some rexx scripts in the \samba directory to add users. Windows 7 can use my server. I'm very inexperienced on Windows, so more of a cookbook is needed. I wonder if my Win 7 Enterprise is different from others for networking.

How do you automatically connect after a reboot?

Greggory Shaw:

--- Quote from: Neil Waldhauer on August 23, 2015, 03:52:56 pm ---
How do you automatically connect after a reboot?

--- End quote ---

In the Samba client I use the auto start under 'File' dropdown menu that puts a icon in the startup folder.

or in Startup.cmd  use something like:

--
evfscli attach h:

evfscli mount smbfs h:\ ;WORKGROUP=HOME;SERVER=SHAW;SHARE=AA;USER=XXXXX;PAS
SWORD=XXXX;EASUPPORTED=1 W

--
something like that not sure if thoses are correct.

Ok, I see 3.3 is dated 10/13 and Samba 1.2 (3.5.21) is dated 7/2013 what are the differences (the TDB files look good in 3.5.21 too) ? All the programs in Samba 1.2 work and had it running for 5 months without problems, do you know what the known problems are with 3.5 ? You may want to check out the updated 3.5.21 server.

Navigation

[0] Message Index

[#] Next page

Go to full version