OS2 World.Com Forum

Subject  :  Connecting Netscape to Web
Author  :  PC350G
Date  :  22 Nov, 2006 on 00:26
From a previous post was able to finally get Netscape 4.61 installed, on 14.062 W4 internal revision Version 4.5
All my computers on P2P Workgroup (win 3.1, w95, w98, ME, w2k, Nt4, XP, AIX ) can ping Warp4 and Warp 4 can ping them. Warp 4 can also ping my router 192.168.0.1.
When I put http://192.168.0.1 into Netscape it just tries and tries to connect but cannot.
Found this article on web

"I use Netscape 4.61 and enter the IP address for the Gateway computer into 'Location:' box. The second issue is more problematic and its resolution is not obvious, or, apparently, documented. The Desktop takes up to 2 minutes to appear on a home network. It seems that Netscape is trying to resolve the location via a nonexistent name server, even though an actual IP address was specified. The solution is elegant: create d:\mpts\etc\hosts and add the following line to config.sys:
set use_hosts_first=1
The usual format for the hosts file is:
ip.address name.internet.domain alias1 alias2 ... #comment
A home network does not have a true internet domain name, so I replace name.domain with just name and repeat it for alias1:
192.168.2.52 nanook nanook #gateway "

I cannot get the above to work.

(1) Is there a special place for "set use_hosts_first=1" to go in config.sys

(2) What is the line supposed to go in the created hosts file at the end of C:\mpts\etc\
I have tried
192.168.0.1 IPEX1 IPEX1 # Warp 4 Computer
and
192.168.0.255 IPEX1 IPEX1 #Warp 4 Computer
where IPEX1 is the unique name given during instal of warp 4
192.168.0.255 pouter assigned to IPEX1
192.168.0.1 address of router.

Any help in connecting Warp 4 via Netscape to internet appreciated.


Subject  :  Re:Connecting Netscape to Web
Author  :  obiwan
Date  :  22 Nov, 2006 on 01:43
Looks like you're using a Class C network. If so, 192.168.0.0 is the network, 192.168.0.255 is the broadcast address. In that case, the IP of your Warp 4 system (or any system) cannot be 192.168.0.255. Try a different IP.

If your router is set up as a DHCP server, use DHCP in Warp.

As for setting variables in the config.sys, in general placement shouldn't matter. I like to make them easy to find.

Whatever IP you assign to your system, put that in your hosts file to refer to the name IPEX1.

code:
192.168.0.123 IPEX1

If using DHCP, just leave the hosts file empty.


Subject  :  Re:Connecting Netscape to Web
Author  :  Fahrvenugen
Date  :  22 Nov, 2006 on 03:37
In addition, check and see what is in your RESOLV2 file (or it might be called RESOLV). You'll find it in:

c:\mpts\etc

It should have your machine's host name, along with the information for the name servers that it is using (although when accessing the machine via a direct IP address, that should not matter).

Another thing, from a command prompt, type:

inetver

and post the results here. I can't recall, but I *think* Netscape 4.61 had some difficulties working with early versions of TCP/IP

My suggestion, now that you have an OS/2 which has a working TCP/IP stack, download the OS/2 Maintenance Tool from:

http://xenia.sote.hu/~kadzsol/os2mt/index.htm

and install the following:

TCPIP_40_0980
MPTS_8423_16bit then
MPTS_8425_16bit

This will bring your TCP/IP stack up to a more recent level.

Alternatively, you can install:

MPTS_8610_32bit and then
MPTS_8621_32bit

The MPTS_86xx will install the much newer 32 bit TCP/IP stack, *however* don't install MPTS_86xx until after you've installed TCPIP_40_0980, otherwise you'll end up with difficulties (officially, TCPIP_40_0980 does not support the 32 bit stack, however people generally no one has run into major difficulties when using them together)

If you install the 32 bit stack, you should be not only able to get the older Netscape4.61 working, but you'll also be albe to install Firefox for OS/2 (or the Seamonkey suite)


Subject  :  Re:Connecting Netscape to Web
Author  :  PC350G
Date  :  23 Nov, 2006 on 23:54
Thanks for replies. Sorry about taking so long to get back to you both but my learning curve of OS2 is really slow as I do not have a good book. Finally landed a couple on Amazon 2nd hand, but they will take 6-8 weeks to get to me in Australia.
Obiwan and Fahfvenugenm
Kept extensive notes when I set up OS2 but on hunting round the setting to use DHCP reverted to manual some how, so set it to auto.
netstat -a now shows 192.168.0.195 given to it by my router.
The next unusual thing is the computer name. During set up the unique name was set to IPEX1 but looking in IBMLAN.ini it says it is CLIENT54.
Put " set use_hosts_first=1 " into config.sys as last line
As I had no C:\mpts\etc folders I created them
Into etc I put a hosts file & tried the following
no entries
192.168.0.195 IPEX1
192.168.0.195 IPEX1 IPEX1
192.168.0.195 CLIENT564
192.168.0.195 CLIENT564 CLIENT 564
Still cannot get Netscape to connect to the internet.
Searched the whole computer and no where is there any file called RESOLV2 or RESOLV
inetver shows version 4.00e
Since I cannot get onto internet cannot use OS2 Mtce Tool to get TCPIP_40_0980 or MPTS_8423_16bit or MPTS_8425_16bit. Could not find a site to download them from to transfer them on CD to the OS2 machine.
On each change of hosts I restarted machine. Is this necessary like in Windows ?
One thing I noticed on installation I had 18 of the xr_m015 zip type files in my FP15\OS2SERV folder
After unzipping csf144.zip in FP15 I then went into the OS2SERV folder and ran " unzip.exe *.zip "
I noticed a message that said at the end successfully unzipped 10 files. I did not notice any other messages during the process about the other 8 files.
On running OS2SERV from the FP15 folder the update went smoothly and during the restart the blue warp splash screen said " 14.062 W4 Internal Revision " and a OS2window with ver said 4.5.
Does this mean all of W4 FP15 went okay ?

Thanks for your patience.


Subject  :  Re:Connecting Netscape to Web
Author  :  dljone9 dljone9@os2world.com
Date  :  24 Nov, 2006 on 00:38

PC350G (23 Nov, 2006 23:54):
Thanks for replies. Sorry about taking so long to get back to you both but my learning curve of OS2 is really slow as I do not have a good book. Finally landed a couple on Amazon 2nd hand, but they will take 6-8 weeks to get to me in Australia.
Obiwan and Fahfvenugenm
Kept extensive notes when I set up OS2 but on hunting round the setting to use DHCP reverted to manual some how, so set it to auto.
netstat -a now shows 192.168.0.195 given to it by my router.
The next unusual thing is the computer name. During set up the unique name was set to IPEX1 but looking in IBMLAN.ini it says it is CLIENT54.
Put " set use_hosts_first=1 " into config.sys as last line
As I had no C:\mpts\etc folders I created them
Into etc I put a hosts file & tried the following
no entries
192.168.0.195 IPEX1
192.168.0.195 IPEX1 IPEX1
192.168.0.195 CLIENT564
192.168.0.195 CLIENT564 CLIENT 564
Still cannot get Netscape to connect to the internet.
Searched the whole computer and no where is there any file called RESOLV2 or RESOLV
inetver shows version 4.00e
Since I cannot get onto internet cannot use OS2 Mtce Tool to get TCPIP_40_0980 or MPTS_8423_16bit or MPTS_8425_16bit. Could not find a site to download them from to transfer them on CD to the OS2 machine.
On each change of hosts I restarted machine. Is this necessary like in Windows ?
One thing I noticed on installation I had 18 of the xr_m015 zip type files in my FP15\OS2SERV folder
After unzipping csf144.zip in FP15 I then went into the OS2SERV folder and ran " unzip.exe *.zip "
I noticed a message that said at the end successfully unzipped 10 files. I did not notice any other messages during the process about the other 8 files.
On running OS2SERV from the FP15 folder the update went smoothly and during the restart the blue warp splash screen said " 14.062 W4 Internal Revision " and a OS2window with ver said 4.5.
Does this mean all of W4 FP15 went okay ?

Thanks for your patience.


"As I had no C:\mpts\etc folders I created them"

It's \mptn\etc rather than mpts\etc

Yes, FP15 looks like it went fine...

But, it appears you did not installl any of the LAN fixes, if INETVER
gives you 4.00e as the version. Install those before trying to get
on the 'net...from any machine, go get them from this web site:

http://www.os2site.com/sw/upgrades/mptn/index.html


Subject  :  Re:Connecting Netscape to Web
Author  :  obiwan
Date  :  24 Nov, 2006 on 23:00
Don't worry about the hosts file. It won't make any difference to whether you can connect to the Internet.

You can set your hostname in the TCP/IP Configuration notebook. Don't worry about the IBMLAN.INI file, it's for the IBM LAN Manager. You can read up on that when you are ready to do file sharing.

It could be that you just need the networking fixes dljone9 mentioned, I don't know. Can you connect to 192.168.0.1? What about with IBM WebExplorer?

If you still have trouble after installing the fixes, post the output of 'netstat -a' and 'netstat -r' and 'nslookup localhost' (the last one just to see what nameserver is being used if any).


Subject  :  Re:Connecting Netscape to Web
Author  :  PC350G
Date  :  25 Nov, 2006 on 03:16
Sorry guys, my saga continues.
Djones
Looked at that upgrades mptn site you said for the LAN fixes and chose wr08707.zip as it had the latest date and biggest file so I presumed it fixes all.
Ran it and got an error signal IBMVL.TX_ not in the \MPTS\OS2SERV\FIX\TRP.2 directory.
Searched my computer and the web for IBMVL.TX_ but could not locate a copy.
A previous poster said to run TCPIP_40_980 MPTS_8423_16bit MPTS_8425_16bit.
I notice that the last two are on the site you gave me but not TCPIP_40_980 and as I was told to run TCPIP_40_980 first, I have never installed these three files as I could not find TCPIP_40_980
What LAN update files should I run ?
Obiwan
I can ping 192.168.0.1 from the W4 machine.
What about IBM WebExplorer you asked.
This was very interesting
(1)WebExplorer(modem) got window Not Connected To Internet. Chose radio button alternate and got the set up window for IBM Dial_up for TCP/IP. I did not fill this in as my router is supposed to be the dialer.
(2)WebExplorer(LAN) get ver 1.2 splash then at next window enter http://192.168.0.1 and get in the body of the screen three blue boardered boxes with a big red X in each. The task bar says connected. 192.168.0.1
On win boxes 192.168.0.1 gives the opening page for my Dlink router and there are three sections, Dlinks title page, a password entry box and a log in button. Clicking on the three X"s produced nothing.
netstat -a and netstat -r gave
[C:\]netstat -a
addr 192.168.0.195 interface 0 mask ffffff00 broadcast 192.168.0.255

[C:\]netstat -r

destination router netmask refcnt use flags snmp intrf
metric
default 192.168.0.1 0.0.0.0 1 47 UG 0 lan0
192.168.0.0 192.168.0.195 255.255.255.0 0 0 U 0 lan0
192.168.0.1 192.168.0.195 255.255.255.255 1 0 UH 0 lan0
nslookup localhost gave
can't find server name for address 203.49.70.20 Timed Out
This 203.49.70.20 is in my Dlink devices window as one of the Domain Name Server addresses. I presume this must belong to Bigpond my ISP


Subject  :  Re:Connecting Netscape to Web
Author  :  obiwan
Date  :  25 Nov, 2006 on 06:06
Well IBM WebExplorer is an extremely ancient browser, and we can't expect much of it, so I am not surprised it won't bring up the D-Link login. What is interesting to me is it claims it connects. Netstat's output seems sane enough, so I'd zero in on the fixpaks before looking any more at configuration.

I'll admit I'm confused myself about the networking fixpaks. You might have a look here for a step-by-step on it:

http://www.os2docs.org/as/tcpip/TCPIP41.html


Subject  :  Re:Connecting Netscape to Web
Author  :  Fahrvenugen
Date  :  25 Nov, 2006 on 19:01
Hi,

First of all, the WR08707 is likely to cause difficulties, I havn't looked at it too closely, but if I recall correctly, it is an update that expects you to have the 32 bit stack already installed, and then it will install updates on that. Currently you have the older 16 bit stack installed, so you'll need to either install wr08610 and wr08621 (to bring it to the 32 bit stack level) or you'll need the wr08423 and wr08425 (to update to the latest 16 bit stack level).

For TCP/IP, you can grab the 0980 update at:

ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/v3.1os2andv4.0os2/universal/un_0980/

These are in .DSK format (IBM's 1.44 floppy disk image format), so the easiest way to extract them is to grab DSKXTRCT off Hobbes:

http://hobbes.nmsu.edu/cgi-bin/h-search?key=dskxtrct&pushbutton=Search

Dskxtrct only runs under OS/2 as far as I know, so you may need to download the images for 0980 and burn them to CD, then extract them in OS/2.

You can find the IBM MPTS fixes at:

ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/

They're also in .DSK format.

To install the updates, you'll need the IBM CSF utility, or you might be able to install using SFIX (which is based on the IBM CSF) from Hobbes:

http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=sfix41&stype=all&sort=type&dir=/

But I'm thinking something else is going on. Since you can Ping your router (and presumably other computers on your network when using their IP address), but the nslookup fails, I am thinking that the overall TCP/IP appears to be working, but something is wrong with the lookup.

Have a look again to see for a RESOLV2 file. It should be in:

c:\mptn\etc

The file should look something like:

domain.name
nameserver 203.49.70.20
nameserver xxx.xxx.xxx.xxx

(where xxx.xxx.xxx.xxx is the IP address of another nameserver - you can list several name servers, and domain.name is your LAN's domain, if you are just working with IP addresses you can leave this as a single word, for example: default)

If this 203.49.70.20 is a domain name server from your ISP, try pinging it and see if you get a response. While some name servers won't reply to a ping, I've found that can sometimes be a quick check to see if you're even getting through to the name server.

Another thing to try is to ping a known domain, such as:

ping ibm.com

and
NSLOOKUP ibm.com

You're not likely to get ping a response, but the PING output should (if the nameserver is setup properly) at a minimum return you with an IP address for IBM.COM (or Yahoo.com or Intel.com or pick anything). If it fails to resolve an IP address from the name, but you *are* able to ping your DLINK gateway, then the problem is most likely in the name server setup. Similarly the NSLOOKUP should give you an IP address.

Another thing to try - from a command line, type:

route -fh
route add default 192.168.0.1 -hopcount 1

And then try your pings again (it is possible that the default route isn't getting set up properly). The Route -fh should flush the route table, and then the second line add the default route.

But if pings are getting through, then you should be able to (at a minimum) pull up the default DLINK setup page in Netscape.

As for IBM Web Explorer, don't pay too much attention to it. It is an ancient browser which can not handle frames. Most of the DLINK boxes that I've seen use frames in their setup pages, so that will very likely fail on IBM WebEx.


Subject  :  Re:Connecting Netscape to Web
Author  :  PC350G
Date  :  26 Nov, 2006 on 03:41
Fahrvenugen, before I had seen your latest detailed reply, for which I really thank you, I went on the hunt again for this TCPIP_40_80 file you mentioned.
I think it is actually 2 files Latest40.exe and un_980.zip on
http://www.os2site.com/sw/upgrades/tcpip/tcpip40/index.html
As latest40.txt was the earliest file I ran it first and BINGO Netscape works and my W4 mackine is on the web.
Have not ran un_980.zip.
There sure is a lot more to W4 and its fix packs than I ever imagined, I sure have a lot of study to do.
Found this over at the os2 NG in my travels, which looks like the correct way to go about updating W4 in a proper sequence.
quote
For OS/2 Warp 4, the best way to get to the latest free level(s) is:

1. Install OS/2 v4 FixPak 15 (XR_M015).
2. Install Device Driver FixPak 2 (XR_D002).
3. Install MPTS version 5.4 (WR_8610) - full product install.
4. Install MPTS v5.5 update (XR_8621) - FixPak. MAKE SURE YOU READ THE
INCLUDED README.TCP BEFORE INSTALLING, and follow the instructions
regarding TCPCOEX.
5. Install TCP/IP v4.0 FixPak UN_0980.
6. Install LAN Services (Peer v4) FixPak IP_8414.
7. Hunt down OS/2 kernel 14.103a_W4 (dated 2005-03-1 and install the
updated OS2KRNL, OS2LDR, and OS2DUMP, as well as the dump formatter
files. Optional, but recommended.
Alex Taylor
end quote
Do you know what Alex means in clause 7 and what the exact correct name of all the files he refers to ?
Have already ordered from Hungary that Upcd to slipstream the whole lot together onto one installation CD.
Will go through your detailed response and let you know the results.

Thanks all, this is a great forum.
Off to watch the cricket, we are killing the Poms.


Subject  :  Re:Connecting Netscape to Web
Author  :  PC350G
Date  :  26 Nov, 2006 on 07:00
Fahrvenugen,. From your last message here are results for your interest.
Found that resolv2, it was created on 23/11/06 after I installed something. It read

Domain
nameserver 192.168.0.1

Pinging 203.49.70.20 was successful 0% packet loss
Here is the screen for the other items you wanted me to try,
[C:\]ping ibm.com
----www.ibm.com.cs186.net PING Statistics----
11 packets transmitted, 0 packets received, 100% packet
loss
[C:\]nslookup ibm.com
*** Can't find server name for address 203.49.70.20:
Non-existent host/domain
Server: sy-dns04.tmns.net.au
Address: 139.134.2.190
Name: ibm.com
Addresses: 129.42.16.103, 129.42.17.103, 129.42.18.103
[C:\]nslookup localhost
*** Can't find server name for address 203.49.70.20:
Non-existent host/domain
Server: sy-dns04.tmns.net.au
Address: 139.134.2.190
Non-authoritative answer:
Name: localhost
Address: 127.0.0.1
[C:\]route -fh
[C:\]route add default 192.168.0.1 -hopcount 1
usage: add destination router metric
(metric of 0 if router is this host)
[C:\]ping 192.168.0.1
PING 192.168.0.1: 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0. time=10. ms
64 bytes from 192.168.0.1: icmp_seq=1. time=0. ms

----192.168.0.1 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet

loss
round-trip (ms) min/avg/max = 0/5/10

My system I suppose is now quite messed up with all the changes and failed fixpacks.
Next week will get another HDD and try again. Want to keep the one install I have.


Subject  :  Re:Connecting Netscape to Web
Author  :  Fahrvenugen
Date  :  26 Nov, 2006 on 18:53
Hi,

Glad to hear you got Netscape working. Admittedly Warp fixpaks can be confusing, especially if you're trying to get the Warp 4 release updated (it can be even more difficult if you're working with Warp 3... not impossible, but difficult...) And I'd forgot about Alex Taylor's web pages, but he has put together an overview of fixpaks at:

http://www.cs-club.org/~alex/os2/fixpaks/index.html

It explains the fixpak situation quite well.

The kernels can be downloaded from:

http://www.os2site.com/sw/upgrades/kernel/index.html

Installing Kernel 14.103a is certainly worthwhile to do, however if your system is booting then it isn't absolutely necessary at this point - in my view it is more worthwhile to get the up and running the way you want it before messing with the a different kernel.

I'm glad to hear the latest40.exe got netscape working. I guess I was correct in my thoughts that Netscape Communicator had difficulty with the TCP/IP that shipped with Warp 4. After time I admit that I forget what all it took to get things working.

It does look like your resolv2 got set up correctly. You're getting IP responses from a name server, so that's obviously working.


Subject  :  Re:Connecting Netscape to Web
Author  :  Fahrvenugen
Date  :  26 Nov, 2006 on 22:52
I just remembered a post that I did a while back on updating Warp... it has some more information too.

http://www.os2world.com/cgi-bin/ultraboard/UltraBoard.cgi?action=Read&BID=62&TID=1102&P=1&SID=sz5obTXjqWeZSovd

Have a look at that thread.


Powered by UltraBoard 2000 <www.ub2k.com>