I'm having problem adding os/2 warp into active directory.How i can map os2 on my file server running windows 2003 active directory.
Hi Max,
please help me out on this - what do you exactly mean by "adding os/2 warp into active directory" ?
Is it that you have a 2003 server and want to see os/2 shares on a different machine from there?
Or are you running os/2 as a virtual machine in the 2003 server and want to make the warp shares being visible through the 2k3 server?
I don't get the picture as to what you have running (and where) and what you want to "see"...
Regards,
Thomas
I asked the same question a few weeks ago without a reply.
In my case the eCS 1.2R system is running on MS Virtual Server 2005. I have a good TCP/IP connection, and I can use FTP to and from the eCS system. But although I can start networking, I can't see any share on the OS/2 box on from any windows computer in the network, nor can I see Windows shares from the OS/2 box.
The OS/2 box can see its own shares. Windows can see the OS/2 box, but cannot see the shares.
Should this work at all? The LAN is Windows Active directory with a couple of thousand nodes.
Neil
Is it a matter of Win not seeing the OS/2-HPFS partition and files within it and OS/2 Warp not seeing the Win-FAT32 partition and the files within it? Could it be solved by installing HPFS support on the Win machine and FAT32 support on the OS/2 Warp machine? ???
8)
Hey all,
Max's situation is as follows (from an email to me):
I have an OS/2 warp client and i want to join this on our domain (active directory).- OS/2 client need to connect to our file server and can access files.
So, the first part I believe means, how can the OS/2 client look to the Win2003 Server for login purposes? (leading into the second)
The second being, how can it get share access to the Win2003 Server to utilize it as a file server?
For OS/2 client authentication and assurance into AD (based on MS implementation of the Lightweight Directory Access Protocol [LDAP]), a Kerberos implementation for OS/2 is necessary.
If the current SAMBA for OS/2 has a decent implementation of the Winbind component, then, the file sharing issue would mostly be dependent on an positive outcome to the first requirement.
The configuration files for the above should be editable by the user so as to customize it for the task of interest (joining AD in this particular case). In other words, any implementation should not be a black box that only the developer(s) will be in an exclusive position to modify --leaving the user outside of it.
...hope it helped :-\ .
I'm on the OS/2 machine and I have the SAMBA client installed. The dialog to use a drive has the following parameters.
Workgroup:
Server:
Share:
User:
Password:
Master: [ Server | Workgroup ]
(name of the master):
memory buffer:
logfile:
log level:
ea support:
Obviously, I need to log in. The netdrive interface to SAMBA isn't really offering that. Does anyone have any suggestions for the parameters listed above?
Neil
...here is some additional high level insight relevant to this thread:
http://www.serverwatch.com/tutorials/article.php/2176201 (http://www.serverwatch.com/tutorials/article.php/2176201)
Evidently, MS improves its alpha products with free software. Notwithstanding, instead of returning in kind, the monopoly engages in the "...destruction of the upstream rainforest where your goods come from." as professor Eben Moglen described in his wiki entry The "Be very afraid" tour:
http://en.wikisource.org/wiki/The_%E2%80%9CBe_very_afraid%E2%80%9D_tour (http://en.wikisource.org/wiki/The_%E2%80%9CBe_very_afraid%E2%80%9D_tour)
By the way, I had the pleasure of being among those in the audience during his keynote speech at the 2007 Open Source Business Conference (OSBC) in San Francisco --he is a powerful orator with strong convictions based on an acute sense of history.
Quote from: Blonde Guy on 2007.09.21, 18:02:20
I'm on the OS/2 machine and I have the SAMBA client installed. The dialog to use a drive has the following parameters.
Workgroup:
Server:
Share:
User:
Password:
Master: [ Server | Workgroup ]
(name of the master):
memory buffer:
logfile:
log level:
ea support:
Obviously, I need to log in. The netdrive interface to SAMBA isn't really offering that. Does anyone have any suggestions for the parameters listed above?
Neil
Neil,
Has the client been created on the Active Directory? I think that should be done 1st.
I'm also looking for confimation that OS2/Warp can log onto a 2003 AD domain.
Is this possible?
I have processes on the OS2 box that communicate with a Sybase DB over name pipes?
Has anybody sucessfully Logged onto a 2003 AD with OS/2
Thanks in advance
joining and loging in are 2 rather different items.
logging in is what most people need probably the hardest.
the biggest problem is that windows 2003 uses kerberos instead of lanman authentication.
so what you need is a kerberos package to get a ticket from the win2003 AD and then a samba client which can handle the ticket as authentication mechanism.
I'm working on such a solution for the netdrive plugin.
Bart
I'm not sure about if os/2 can login to a windows 2003 domain server or not to get full active directory access without some third party tool, but I do know that IF the only thing you care about is having shared folder access then you don't have to login to the domain to get it. Windows 2003 server offers a "workgroup" name for computers that do not have domain login access which will give you access to shared folders. OS/2 & ECS can login to a workgroup with built in networking. If this solution would meet your needs, let me know and i'll post detailed instructions.
I for one would be very intereted, I cant see many shared folders on my schools networks, though I know there are plenty.
Hi Saijin_Naib,
I haven't actually tested connecting an ecs machine yet to my office 2003 server via workgroup. I have connected my ecs machine to a windows 2000 server via workgroup however, so I think it should be about the same.. and I have connected several macs & XP home machines to my office 2003 server via workgroup with similiar methods so combining my knowledege I THINK this should work for you or at least get you going in the right direction-
I believe this is the default setup for windows 2003 servers: (or at least this is how we have managed to set it up at my workplace) A normal domain is something like domainname.net, which the domain computers connect to for full active directory access. But we have some computers in the office (such as windows xp home and mac machines) that do not have the ability to connect to the domain and can only have peer-to-peer workgroup access. In such cases they login as a workgroup, with the workgroup name domainnamenet instead (so basically take whatever your domain name is and remove the . to get your workgroup name).
On the Windows 2003 server side you would-
(1) In the servers tcp/ip settings you would want to allow netbios over tcpip. I think this is already setup on all windows systems by default, unless an admin turned it off, so you might want to just leave things as they are and test if it works before changing things :).
(2) The shared folders on the server that "workgroup" computers can access have to be given read/write permissions set to allow "Everyone" to work (or just read permissions if you don't want to write). If the folder only has access to specific domain users, I think you would be locked out.
(3) Windows requires some registry changes to allow networking to work with ECS. This is a change I needed to make on windows to connect to a win2k server:
--
For W$ 5.0 you need SP4 (and for W$ 5.1 SP1). Additionally, you have to
add a registry setting:
| 1. Click Start, click Run, type regedit, and then click OK.
| 2. Locate and then click the following key in the registry:
| HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
| \Services\lanmanworkstation\parameters
| 3. On the Edit menu, point to New, and then click DWORD.
| 4. Type EnableDownLevelLogOff, and then press ENTER.
| 5. On the Edit menu, click Modify.
| 6. Type 1, and then click OK.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;323582
--
There might be others that you need for windows 2003 unfortunatly that I am not aware of.
(4) On any Windows Guest macines or other Windows machines on your LAN, make sure you go into regedit and search for all entries of LMANNOUNCE and change the values from 0 to 1 which will make that macine show up on the NET VIEW command or on the network browsers for both Windows and OS/2
On the ECS/os2 machine you would:
(1) You need to make sure "netbios over tcpip" is added to your network card. I believe ECS does this by default during installation if it auto detects your network card. If you set it up manually you can add it by running MPTS (located in the OS/2 System->System Setup folder). Just edit ethernet adapters. Click on your network card and click on "IBM NETBIOS OVER TCPIP" on the protocol list, and click "Add". You'll then see it appear under your network card in the bottom window as "0- IBM NETBIOS OVER TCPIP". You then click that entry and click "Change number" and enter a new number (as 0 is usually already used by another entry already under the network card, so change it to 1, 2, or 3 for example).
(2) On os2 & ECS you need to setup your network unique username and "workgroup" to be setup as the same as your windows 2003 server network workgroup.
To do so you run Local system>install/remove>Post Istallation. On the post installatio program there is a tab for network username and workgroup. Just enter something unique for the username (for example I used davidos2), a password, and then enter the workgroup for your windows 2003 server as I decribed above (such as domainnamenet).
Save the post installation task.
(3) If you did all of the above you should be able to now login via running local network/lan login (workgroup). It will prompt you for a username and password to login to the workgroup, just enter the username and password from step 2 above and click to login. Hopefully in a few seconds it will report that login was successful.
You then click to load "start file and print client" in the same networking program list (under local network) and wait for the file and print client to load up.
(4) You can now browse shared folders using the "file and print client browser" to view public folders on the other workgroup computers including the windows 2003 file server.
You can add a network drive letter by running local network/sharing and connecting. This will show all of the computers available on the workgroup, allowing you to browse for a specific folder and assign a drive letter.
You can also share any os/2 file folder to the rest of the windows computer now by right clicking on the folder you want to share and choose "properties". If you're logged on to you workgroup you can click on "Shares" and there you make the settings for sharing the specific folder (allow everyone access).
Hopefully the above is useful in some way :). I was pretty vague on some details so if anything is unclear feel free to ask for more.
No, its very descriptive! I will try this right away, and tell you my results!
I must reboot into eCS, but here is what winXP shows for my WorkGroup directory.
Okay, I have followed your instructions and here is what the File & Print Resource Viewer shows under eCS. As you can see, its quite a different picture. WinXP shows 42 shares, eCS only 6. Why is this? Im quite terrible with networking, and I don't really know much about it, so please excuse me if I am asking a stupid question here.
Hi Saijin_Naib,
It's not at all a stupid question - it is a bit of a mystery.
Let me just ask:
(1) Is your network using a domain setup or simple workgroup only - meaning do you have a central server that all of the computers login to, or have you just setup each machine to have the same network workgroup name and connect to each individually?.
(2) The 6 computers that you can see from ECS, are any of them windows machines? (I see two of them are alternatives OS's - one being a mac and one ECS apparently. So I was just curious if all of the visable ones are not windows machines or if you have any windows machines visable from ECS).
(3) With the 6 that you do see, how do they logging into the network?
On the positive side it seems you have to ECS end setup correctly, if you can see ANY machines from it. I would think this problem is likely on other side.
OH I just realizes you said this is a school network. So maybe you don't have access to answer all of those questions?
Well just let me know if you do know, for example, if those 6 computers are not windows machines.
The first eCS machine is my own :)
I believe the other machines are all OS-X machines :\
I think my network is just a series of Workgroups. I can browse them all using WindowsXP so I can see what other workgroups are there.
Can I not see the windows machines because of something? Is this what the Samba Client is for?
Below is what the Windows Network browser shows me for the top-level workgroup listing.
Hello Saijin_Naib,
This is my guess as to what is happening:
For ECS to see each windows machine on the network (and for windows machines to see your ecs machine) - each of the windows machines must have some minor changes to the windows registry changes (like changing LMANNOUNCE in step 4 on my original post).
Since I assume you do not have access to these machines (other students) and they likely didn't make those changes, you would not be able to see them in your network browser on os/2. If you have a friend with a windows machine (and they don't mind you messing with thier system) you could test this theory by making the registry changes I discussed.
It seems mac os x doesn't have that issue and allows you to see them correctly by default.. dam microsoft! :).
So you could theoretically make it work if you go to every other computer on the network and make the registry changes needed :)..
I'm not sure if you used a samba client if you would still need to make those registry changes on the windows machines or not - maybe the samba client would make your ecs machine act like a windows machine and therefore make the registry changes no longer needed. Unfortunatly I do not have experience with samba on os/2.
Let me know if i'm making any sense or not.
I'm in a difficult position. Our Domain is Currently NT4, This is now migrating to AD 2003. What this means is, we will no longer have control of our Domain. So I wont be able to make any changes to the DC.
Our OS/2 Box network settings is authenticating against our NT Domain. We don't connect to any shares and don't exactly logon. Our Serives run in real time and connect to a Sybase DB over name pipes. does anybody now if NamePipes is dependant on OS/2 having authenticated on a AD level?
Thanks again
Hi Blondzer,
Though I am not sure, I would guess since all of the NamedPipes implementations I have played with are in the format SERVERNAME\\PIPE that the machine would need to be authenticated in some fashion, whether in the share environment or in the domain environment. That would make the most sense to me, but I have virtually no familiarity with NT/Server 2K3 setups so am not sure (I would think it a glaring security hole though, if the server or other workstations would accept connections from a NamedPipe from an un-authenticated machine - though MS may disagree)
-Robert
Yeah, you are making sense. I cant go around making registry changes however :P
I gotta see what the deal with Samba is and how I can use it to get on the network here...
Okay, so without any modification my roommate can see my eCS machine perfectly, as well as any shares I have. He can also access my shares without any issue what-so-ever! So it works in one direction, so I guess thats not a bad thing. I however, still can not see anything but the OSX machines on my network. I had him add the lmanannounce key to his registry to see if I can then see him on the network as well, but it had no effect. He can also see an Ubuntu machine on the network.
Quote from: max on 2007.09.19, 07:46:30
I'm having problem adding os/2 warp into active directory.How i can map os2 on my file server running windows 2003 active directory.
FWIW - some progress is being made on this. Using a java kerberos client, and a kerberos enabled build of samba, we've been able to browse resources on a win2k03 server using eCS.
Next I need to debug why kinit (from kerberos) isn't working correctly, and integrate the necessary changes into Netdrive to make the access more seamless.
Stay tuned.....
Cheers,
Paul.
Quote from: Paul Smedley on 2007.11.20, 04:19:45
Quote from: max on 2007.09.19, 07:46:30
I'm having problem adding os/2 warp into active directory.How i can map os2 on my file server running windows 2003 active directory.
FWIW - some progress is being made on this. Using a java kerberos client, and a kerberos enabled build of samba, we've been able to browse resources on a win2k03 server using eCS.
Next I need to debug why kinit (from kerberos) isn't working correctly, and integrate the necessary changes into Netdrive to make the access more seamless.
Stay tuned.....
Update: I hacked the source for smbcd.exe and once you're authenticated with kinit (the Java version) I've successfully browsed a share on a Windows 2003 server using Netdrive.
Still working on debugging the C version of kinit - looks like a select() call is the problem, but if anyone wants to play around - please contact me for a kerberos enabled smbcd.exe and a mudmap of how to set it up - paul at smedley dot id dot au.
Cheers,
Paul.
An open source entry level solution from LikeWise (http://www.centeris.com/products/likewise_open/) (at LinuxWorld 2007, the organization still called itself Centeris) might speed up and simplify this ongoing effort on the OS/2 side.
The binary distribution for certain Linux distros, as well as the source for the (AD client) LikeWise Open agent, are available by selecting the Download tab at their website. Users, system admins, as well as developers, are encouraged to contribute to the LikeWise Open project. However, if you are a developer and want to contribute with your efforts, you are forewarned that you should not have signed a pact with MS:
Important: In order to avoid any potential licensing issues we require that anyone who has signed the Microsoft CIFS Royalty Free Agreement not submit patches to Likewise Open, nor base patches on the referenced specification. We require, too, that patches submitted to Likewise Open not infringe on any known patents. Finally, as with all GPL work, the submitter should ensure that submitted patches do not conflict with any third-party copyright (http://www.likewisesoftware.com/community/index.php/participate)
Cheers!
It looks like this thread ended without coming to a working conclusion.
I've got access to the Windows 2003 AD domain again, and I'd like to continue trying to browse shares.
Like most people attempting to do this, I had everything working with Windows 2000 server and OS/2 File and Print Client, but the Windows network changed and I'm no longer able to do anything useful on the network.
Also like most people trying to do this, I have a very limited understanding of Windows 2003 AD networking.
Does anyone have progress to report, or suggestion of how to continue?
I posted the NetDrive SMB plugin settings -- there appears to be little or no documentation of what the parameters mean. Even if the SAMBA client does work, I'd need to have some guidance to set those parameters.
Anyone else still trying to get this working?
I (a client) has an eCS machine hooked up to the same network as a Windows 2003 AD setup. I'll see if I can figure something out there the next time I am out there, failing someone else coming up with a solution.
Anyone who has ideas, please post them... I may not get to this until late August - and even then, I'll be fiddling around to try to make it work... very limited experience with AD here.
In the meantime, I did find this post that seem to indicate some possible things to try:
(Enabling Mixed Mode for AD):
http://www.computing.net/answers/os2/os2-warp-and-ms-active-directory/2225.html
Robert