I've just recently tried networking my Warp 4 machine to another PC running NT 4 (I got tired of rebooting through Boot Manager to access Windoze.) I can get NT working on the network between the two PCs, but not Warp and NT. I am using a 5 port hub (not a router) and NT Workstation, not Server.

When I try to start the network connections on Warp, The Requesters takes about 1 to 2 minutes to initialize, which is followed by a message stating that I have a problem with my cable connection, which is bunk. My friend who is quite conversant with OS/2 said that he had this problem several years ago and overcame it by either adding/removing various protocols and even disconnecting the cable before rebooting. Some combination worked for him,but he can't remember which it was. I'm still stumped. Any ideas out there?

Thanks.

First what protocols are you using?
Also are you using the correct OS2 drivers for your network card?
You are not just accepting the ne2000 compatable driver are you?

Warp4 should connect to the network without mush effort at all.

Try it with just netbuie as the network protocol first.

Dear, Hmmm,

I'm using a 3Com 905B-TX Fast Etherlink XL PCI card and the resp. drivers that I downloaded from their site. When I boot up OS/2 it states that the card is found on "PCI slot 19 using IO base EC00h on Interrupt 10." So this seems not to be the problem. Originally, when I purchased my second computer, the supplier could get me only one 905B card, the other is a 905C. I had the 905C card in this machine but OS/2 couldn't recognize this model, so I switched it around with my NT machine.

My current MPTS configuration is this:

3Com Fast Etherlink/Etherlink XL Family OS/2.....
0 - IBM OS/2 NETBIOS
0 - IBM TCP/IP

I do not have the TCP/IP for lan configured as yet; I understand that is not necessary at this time.

Thanks again.

I beleive you will need tcpip configured as both protocols you have listed require settings from it.

Try NETBIOS (this is loaded over the top of tcpip)on interface 1 for the card.

Sorry I stand corrected I'm getting my wires crossed NETBIOS is the equivalent to NETBUIE.

Hers's a kink on OS2 networking.

http://www.deltasys.org/network.html

I've just checked my Warp box and the protocols are set as follows:

1 IBM OS2 NETBIOS
0 IBM OS2 Tcpip
0 IBM NETBIOS over Tcpip

Dear Hmmm,

Thanks for your input.

I tried configuring my MPTS according to the three lines you mentioned in your last message,however, I received the following error messages on boot up:

NET3406: an error occurred while opening network device driver NET1=NETBEUI$.

SYS1719: the file D:\IBMLAN\NETPROG\NETWKSA.200 specified in the IFS statement on line 188 of the config.sys file does not contain a valid device driver or file system driver.

You mentioned in an earlier message that both NETBIOS and TCP/IP need some configuration parameters. Do you know what has to be added or changed in these fields other than the default settings? IBM's online help files describe in detail what most of these parameter fields do, but there is no info given as to what values are meant to go into these slots. Is there some web site that has this info? Setting up a network should be easier than this!

Thanks again.

This page should help-

http://www.deltasys.org/tcpip.html

Its important that you enable the interfaces being used or you'll get nought on tcpip.

Setting up networking isn't too hard on warp. Its just that its different than windows. I know I had trouble at first.

I'm no expert lol.

Sorry I'm late to the party.

Anytime I get that err, is that either my cable wasn't detected or the card died.

Try the following:

Remove the NIC from the OS/2 box and reboot.

If you get the same err, then it is the card or protocols.

That card is rock solid in OS/2, so drivers are out of the picture.

There are some INI files that you will need to clean up in addition to the config.sys. Looks like you got several lines that don't point to the right protocol.

I would remove networking in OS/2, then clean up ini and config.sys files, then reboot, make sure it is a clean reboot. Then reinstall networking:

3COM NIC :
0 - TCP/IP
0 - Netbios
1 - Netbeui

Reboot, then make sure it can start lan requester by logging it or enable it at start up (check file and printer sharing client config).

Do this while there is no CAT5 plugged in. If that works, then plug in the CAT5.

I use a CLASS C network address range:

192.168.123.X (X = 1 - 254) - IP
255.255.255.0 - Subnet

Enable Loopback device to be able to ping yourself.... then add HOST routing entries on OS/2 box.

Sorry I meant: NIC Cable instead of:

"...Try the following:

Remove the NIC from the OS/2 box and reboot.

If you get the same err, then it is the card or protocols....
"

Was wondering where you got to Peter.

Peter,

Thanks for the input, but I'm still not there, yet.

I tried the setup routine as described on the Deltasys. website, but no luck. I now get an error message on boot up that states:

ifconfig:ioctl (SIOCDIFADDR): no such interface

SIOCADDRT: Network is unreadable.

I'm not clear on page 1 of 2 of the hostnames tab of the TCP/IP config. Is this section necessary if I am not part of a domain? I'm just 2 computers without a centralized server. Page 2 of 2 of this tab has a config. window called "Hostname Configuration without a Nameserver." Would this not be the only section that applies in my case?

My goal right now is to network between OS/2 and NT, then I will install an ADSL modem into my hub and set up the Internet through that.

Any further suggestions on what to do? I uninstalled the networking (pain in the butt because it removes all the install icons, but I recorded the location of the Peer and file services icon this time.), cleaned up the config.sys file and rebooted.

Hmmmm... yeah, not on internet much at home, but once I get cable (this Sat.) I should be on more... I'll document my trials there, I got a Linksys router with W98SE client, Linux client, and OS/2 WSeB/Warp box.

John: I *think* ifconfig is part of MPTS.. I have a feeling that you got something left behind. I am assuming that you got this err when you reboot after you uninstalled?

Have you created archives at boot up? If so do you have an archive that ever worked?

When I get home tonight (7:30 am), I'll get my config.sys and network INI files and see what could cause that...

I'll also get some print screens of the TCP/IP tab in Warp 4... my WSeB is setup with DDNS and DHCP, so TCP/IP is setup differently with the routing host tables...

I spaced last night, I'll try again tonight.

Sorry about that.

Peter,

Re. responses 11 and 12, above, I got that error message after I tinkered with the TCP/IP settings; left in default mode (ie, empty) they weren't there.

I never had a configuration that booted properly. Upon boot up, before tinkering with TCPIP, the Network Messages window would start up, If I tried access it, I got a message stating that the requester was not started. If I try to log on thru IMBPEERS, for example, the requester attempts to start, but fails, giving me the usual cabling error message. However, another menu screen appears asking for my user ID and password. When I enter these, they are accepted, but the requester is still not running. So it seems that the sharing printer and files or IBMPEERS utilities is working, except for the basic requester function.

Hope this is of use.

Oh, one more thing. Does the fact that the interface card on my NT box is not recognized by OS/2 have anything to do with it? A friend of mine thinks it shouldn't since it is going through a switching hub. I have a LinkPro SOHO 10/100 5 port hub.

Thanks.

No, the other PC's NIC does not matter, unless you need the MAC address, and drivers aren't involved there either.

If no configuration worked, then you might need to reset the BIOS on the NIC. 3COM has a flash utility on their website that you boot to DOS to reset the IRQ, etc... try that out.

There is a log that gets created when the requester fails.

Requester starts several "services" via the "Net Start" command... (e.g. "Net start server")the log shows this. I forget the name of that log (similar to NT Event Viewer).

Is there a possibility that you can try out different NICs? What happened when you tried to boot the OS/2 box without the cable being plugged into the NIC?

Sorry, no print screens, damn Wink virus attacked a computer at my in-laws.

I found this: http://www.os2ezine.com/v2n10/cable6.htm

It has all the pictures one could want.

Peter and Hmmm,

I've been playing with the system all day and still no luck. I even downloaded a fixpak for IBMPEERS and LAN REQUESTER located at http://www.warpupdates.mynetcologne.de/english/net_peer.html, but to no avail.

A help line linked to this site states that the "Domain" mentioned in Warp is in fact the "Workgroup" in NT. Is this correct? I have NT Workstation, not Server, so my Domain naming abilities are somewhat none-existant.

From what I can tell, my problems with the Requester are totally independant of what is happening on the NT box; the requester has to start on the Warp box before anything else happens, correct?

I'll continue pulling my remaining hair out this week.

Thanks for you continued input.

Hi guys.

John did you enable the loopback adapter and try to ping with-

ping 127.0.0.1 in an OS/2 window?

He hasn't answered any of the questions, so I am dropping it... no sense in helping if he doesn't answer some of the questions... :-|

This might be helpful: the errors are logged in \ibmcom\lantran.log - this file contains any errors found while initializing your NIC. OS/2 gets the NIC model wrong plenty of times during installation and will usually select a driver which believes it is appropriately addressing the NIC...it is only when networking is started (net start) that the problem shows up.

Generally OS/2 networking will come up unless:
- There is a problem with the NIC
- There is a server on the same network with the same machine name
- You are attempting to bring up domain services and the domain controller does not recognize your machine.

Getting the networking to talk between the machines will require a user network login, etc., but just getting OS/2 networking to come up does not...it just requires the correct drivers and a machine name at the domain controller (assuming you are using domain and not peer validation).

Peter and Hmmm,

There are times when one is not chained to the bloody PC.

The answer to your question is that ping does not work. Yesterday it just scrolled down the screen giving me an error message--can't remember what it said. Today, after some more tinkering on TCP/IP settings, PING states: "56 data bytes" and hangs.

Yes, I enabled the loopback and tried pinging to it. I get a scrolled message of "64 data bits...etc." the sequentially iterates.

Essentially, I've tried everything in the book and no luck. I will look into Rick's idea in reply number 21, above. I have a suspicion that the problem must lie with the NIC.

Thanks again.

Rick,

Attached is the lantran.log file; it appears that the NIC may be the problem.

BM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
IBM OS/2 TCPBEUI 5.05.0
TCPBEUI: Using a 32-bit data segment.
IBM OS/2 NETBEUI 5.00.0
NETBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( Dec 05, 2000)

IBM OS/2 NETBIOS 4.0
Adapter 0 has 75 NCBs, 30 sessions, and 6 names available to NETBIOS applications.
Adapter 1 has 225 NCBs, 130 sessions, and 20 names available to NETBIOS applications.
NETBIOS 4.0 is loaded and operational.
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
PRO0028: A hardware failure occurred when the program tried to bind VECTOR to EL90XIO2_NIF.
TCPBEUI: completed initialization and is bound to TCP/IP network interface lan0.