I installed all the netbios over tcp/ip on an OS/2 warp v. 4.0 machine. I also went in to install/remove directory and installed the networking part and it asked for the NT domain, IP Addresses, ID and Password, etc... I also went into MTPS and configured the netbios over TCP/IP to H-node and also added the WINS server IP to the broadcasts. After the reboots, I went to a dos window and tried to use NET USE G: \\server name\share. It tells me that "net is not recognized as a internal and external program..." Is there another thing that I am forgetting? Bare in mind, I am learning OS/2 as I go along. Thanks for anything you can give me. Chris

On my OS/2 Net.exe ist located in \Ibmlan\netprog; i think its part of the peer weeb services; if you succeed to connnect os2 to an NT Server please contact me. i have currently the same problem, ping, www, alle the stuff is doing well, but i didnt succeed to connnect to my NT Domain. Good Luck. Markus

First off is your NT server running netbios? if you can or are using tcpip try using ibmtcpip also differences exist between DHCP or FIXED IP addressing.If using netbios get the latest netbios for OS/2 at http://techsupport.services.ibm.com/asd-bin/doc/en-us/catalog.htm toward bottom of page called NetWare Client for OS/2 2.12

I have a simular problem. NET START REQ working find. But when I try to LOGON I got th message "The remote node or domain server is not currently available.". This message is only appear when running Ethernet cards. When running Token-Ring cards it works find. But I don't know how to make it work whith Ethernet cards, so if you can tell me how to make it work whith Ethernet cards I be very glad.

Same problem. I can't seem to connect to a NT server. Running warp4 installed Fixpack 12. If anyone finds any notes on this please let me know.

1. It seems, that you didnt install the peer-services again. I did it here the same way like you - but i had to reinstall the peer-services. After that it worked fine. its really important to know, which Protocol your server is using - at least Netbios over IP is recommended (thats really functional ;-))) 2. For logging onto a NT-Domain, its important, that you have a look onto your netcard. There are some Candidates that have big Problems with using more than one Protocol at the same time(the Problem with the Ethercard, that wasnt with a Token-card). I've learned that the same way you do ... For solving that Problem you MUST use Netbios over IP and NO OTHER Protocol! It's really intersting: Using only Netbios, there is no way to see the Data in the shared resources in the Network-Folder on the PM - only after connecting to a Network-Drive (like x:\) you can see(and use) them - and only from a commandline! really funny, isnt it?