• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

How to access Win2k3 shared drive from Os/2 warp server

Started by prem055, 2009.09.14, 11:53:24

Previous topic - Next topic

prem055

Hi

Can some one help me in accessing the shared drive on a win2k3 server from OS/2 warp server (ver 3.0) and please note my Win2k3 server is alone part of the Active directory.

warpcafe

Hi,

there's a lot of people who do know much more than me about this, however they seem to be busy at the moment so I will try to do my best. As I don't know how savvy you are about all the involved things... please bear with me, let's see what things are like so far.

Can you give a try and tell me what happens if you
- go to an OS/2 command window
- enter "net view \\<w2k3_server_name>"
  (without the quotes and <w2k3_server_name> replaced by what your windows servers is named)
  e.g. if your w2k3 server is named ORBIT you enter
  net view \\ORBIT

I suspect you will get a NETxxxx error in return telling that teh server or network name is not found... or similar.

Next, what is the share defined like on your w2k3 server? Meaning: What type of access (read, full, ...) for which users?

And by the way, what do you mean "my Win2k3 server is alone part of the Active directory" ?
(...that there is no other windows server in that domain?)

Thanks, Regards,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

warpcafe

Hi,

found this one here at os2world.com... you'll have to scroll down a little up to where "os2monkey" provides a cookbook to "Saijin-Naib":
http://www.os2world.com/forum/index.php/topic,380.0.html

On the overall impression, it doesn't look too good... but I don't know what the current situation is like since the last posts to the given thread are more than 1 year old... perhaps everything works today? :-P In any case, RobertM, BlondeGuy and some others come to mind when it's about people who are savvy on OS/2 networking here at os2world.com.

Note:
If all you get from the link is a header and a footer (with no contents in between) then you're suffering from the problem we still have with the parts that connect CMS and Forum. In that case, try to see if logging-in (or logging out if you're logged-in) makes a difference.
If neither way works, go to "www.os2world.com/forum" and in the search box (top, right) enter
"How ican join OS/2 on active directory" (include the hyphens in the search term).


Hope this helps
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

prem055

Hi

What I meant by saying only the win2k3 server is part of the active directory and the Os/2 is not part of the active directory. what you say is correct i do get a netXXX error message .

My requirement is just to map the win2k3 shared drive and access the shared folders from Os/2 ,using a net use command .



warpcafe

Hi there,

well, ok, I will try to explain what I would do in that case.
Note that this may be far from being "the correct" or even one right approach... but I'm still confident that the fellow readers here will chip in with additional help once they notice I am doing something wrong... :)

Please note that right now, for the Windows part I'm only having an XPSP2 at hand, as well as "only" an eCS 2.0rc6 running in VirtualBox for the OS/2 side of the story. A big part of what is written comes from memory (if that serves...) so please don't go word-for-word with my "instructions" but rather check what comes closest in wording and meaning for your systems.

The short story would be:
1) enable "netbios over tcp/ip" on both machines (or make sure it is the case already)
2) share the folder with full access to "Everyone" on win2k3
3) make sure the OS/2 machine uses the same workgroup name as the w2k3 (should be "workgroup")
4) run net use R: \\<w2k3-server-name>\<share-name> ("R:"= drive letter to be assigned to share on OS/2)

Step 3) in my mind the most critical one because a) I cannot tell you where to edit/view that setting on your Warp Server and b) you may not WANT to change it if you are running network services on your Warp server for a Warp server domain :)
Unfortunately, there were quite some differences between the setup GUIs for Networking on Warp server, client, and now eCS. So your mileage may vary. ;)

The long story:
To start off with, you should make sure that your w2k3 server and the OS/2 machine are able to understand each others gossip by making both use a flavor of Netbios on their network cards. (Or: Check if all is set up like this...):
For Windows, that means
- bringing up the network properties dialog of the NIC (Network Interface Card )
- checking that the "file and printer sharing" is checked
- for the TCP/IP protocol, launch its "properties", select the "WINS" tab and click "advanced"
- there should be something with "Netbios over TCP/IP" and it should read something like "enabled" ;)
For OS/2 that means
- bring up the MTPS configuration
-- either: in an OS/2 command window type "MPTS", enter
-- or: in the system configuration ("somewhere") search for "Adapters and protocols" icon, launch
- click "configure MPTS"  (or -since default option- simply press enter key)
- select "lan adapters and protocols", click "configure" (or -since default options- simply press enter key)
- the next screen shows a llist of adapters, a list of protocols and a list that shows what is currently active (1 network card name, 1 to many protocols listed beneath it)
- check if there is a protocol entry for the card named "IBM OS/2 Netbios over TCP/IP"
- the leading digit is the "logical" adapter number. The important thing is that "IBM TCP/IP" and the Netbios one must have the SAME digit, other protocols (like "NetBEUI" if listed) must have a different one (1, 2,...)
- If that is the case, you can escape that mess with cancel/cancel/close
- If not, you will have to add the "Netbios over TCP/IP" to the adapter:
-- in the lowest list, click (select) the network card
-- in the middle list (protocols), click (to select) the "IBM OS/2 Netbios over TCP/IP" entry
-- the middle list should pushbuttons assigned with it with one of these reading "Add protocol": click this
-- that should add the protocol ("Netbios...") to the adapter
-- now make sure that the logical adapter number for "Netbios..." is the same like for "TCP/IP"
-- you can do this by click/selecting the "Netbios..." entry and clicking the pushbutton "change number"
-- enter the number as required

That was part 1. Now both machines hopefully talk and understand "Netbios" stuff.

In part 2, you will have to make sure that the w2k3 server share is accessible for "everyone".
We should do this because all other nifty things like special user ids / groups / passwords would certainly require some kind of authentication mechanism that OS/2 cannot provide to win2k3... "kerberos stuff" and so on... so let's just give full access to everyone for that share.
I suppose you know how to do this - nevertheless:
- In windows explorer, navigate to the folder you want to share
- right-click it, select "sharing and security"
- select "share this folder", give it a name and go to "permissions" tab
- enable full access for everyone
Note that I remember there was once a way to create shares on windows machines (w2k and above) by using "simple sharing" (user name, password) instead of full-fledged AD style. If that is feasible somehow, it would ease the process... but I doubt we can get this to work.
By the way - have you got admin rights at all for the windows machine and can access it to change settings?

Part 3, as mentioned above, well... sigh.
You could check what is stated in OS/2's IBMLAN.INI that should be located in \IBMLAN.
Try to see if it shows a line like "domain = WORKGROUP" in the [requester] section (be careful, there's tons of comments below the [requester] before you get to the actual entries lines...)

Part 4 - give it a try.
Preferrably use command-line tools instead of GUI-like stuff like neighbourhood browsers etc. since these may contain additional overhead that slows down the returning of results.

That's all I would do... and in case it doesn't work, there's still stuff to do like using name tables for IP adresses, what the heck. Is it crucial to have a >share< being accessed or is this about tgransferring files in any way as long as it works? In this case you'd be better off with Filezilla Server on the w2k3 machine and any FTP client on OS/2 :)

But be aware, finally, that all the above might turn out as useless crap because Warp simply CAN'T deal with anything ActiveDirectory (unless it's done by a Samba client perhaps...)

Hope this helps anyway, even if only setting the base for my more savvy mates to follow-up on.
Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

prem055

Hi

I need to access the shared drive folder of win2k3 server from Os/2 warp server
My win2k3 server is part of the active directory and Os/2 is not ?
Please advise

regards
Prem

Blonde Guy

There's a setting in Windows Server 2003 that allows Windows for Workgroups to see the share. If this is on, then OS/2 can see it also.
Expert Consulting for OS/2 and eComStation

prem055


prem055

hi

Could someone let me know , how to access the win2k3 shared folders from OS/2


Prem

warpcafe

Hi Prem,

you have already opened a thread for this today, let alone the thread you originally opened some weeks ago. This makes for a total of 3 threads on the same question. Please make an effort to use your existing threads for updates... and please also allow for others to think, eat, sleep in between giving you answers.

If you have opened this thread here because you have trouble accessing the older one(s), please tell us so and we'll see if you are victim to our little Joomla-SMF-bridge problem and we'll tell you a workaround.

But please refrain from opening more threads for this - repeating a question doesn't help in stressing its importance but rather annoys others and prevents you from getting a response.

Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

prem055

hi
Thanks for the reply, I have already done the same on my Os/2 and win2k3 server end
but when I use a net use command to map to the win2k3 shared folder it just throws network error 53 path not found.

do i need to enable any thing on the win2k3 server end , like local policy settings etc
or any host file entry on the os/2 end
I'am unable to attach to the win2k3 server either by using IP or hostname ?

only able to Ping using the IP address, but If I ping to my win2k3 server(test123) using the hostname no response it fails.

warpcafe

Hi prem,

for the ping, it seems that your DNS is misconfigured, since it works via IP but apparently is unable to resolve the hostname to an IP adress. Give it a try with "tracerte test123" (in a command line window) and let us know what it says.
Although I am sure it will work, also try "tracerte www.yahoo.com" or any other URL - just to make sure that there is no general problem with your TCP/IP.

For connecting to the win server, "netbios over TCP/IP" is used. That means, that the Netbios packets are wrapped into TCP/IP and sent to an IP adress (not "host name"). Therefore, if you are able to ping the win server by IP adress, the basics are working.
Next, netbios names (as far as I know) are NOT resolved by DNS or the hosts file but by some other flavor:
- Run "mpts" from a command-line and
- OK/OK your way to the list of adapters and protocols
- for the "netbios over TCP/IP" entry in the last listbox, select it and click "edit"
- it will ask what to edit: Select "names list"
=> try to add an entry with the netbios name ("test123" ?) and IP address for your win server
- Exit by saving changes, eventually reboot if required (I bet it is...) and see if that makes a difference

Sure there is a config-file-edit way of doing this instead of clicking through dialogs, however I can't tell by heart what that was. Sorry. I still believe however that there is something else fishy with your OS/2 networking setup in general... or with the w2k3 server behaviour, see Blondeguy's explanation.
(Hopefully he can get back on you with the required information, I don't have a w2k3 server at hand to check where that setting may be hidden... perhaps google can help on that at least?)

HTH, Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

prem055

hi

Thanks for the reply, I managed to map the win2k3 server (part of workgroup), but by Os/2 server crashed and I'am in the process of rebuilding the same .

Next step I need to add the win2k3 server to Active directory and then map it from Os/2 let me see what challenges I face.
would posted with new problems if anything crops up again

RobertM

Hi prem055,

I have merged all of your topics on this same question here. In the future, please refrain from multiple posting of the same question.

Best,
Robert


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


prem055

hi Robert

thanks for the same, I'am in the process of  adding my Win2k3 server to Active directory . post which I will have to check if I get into any more trouble.