On Sun, 27 Apr 1997, Robert Wu wrote:
> We have a Win95 PC here that I'm trying to install the above
> product onto. On all of our other PCs, we use either Reflection
<snip>
It sounds like a configuration problem (and one I've hade). You should be
able to connect to LAN devices (like the Novell server), WAN devices
(like HP 3000's on remote LANs), and an ISP all at the same time. That's
what I'm doing right now. I'm logged onto the Novell 3.11 server, logged
onto 3 HP 3000's (one locally, two in other parts of the world), and I'm
dialed into my ISP (Internet Service Provider) with a PPP connection.
The dial (PPP) connection is presently supporting the telnet session
through which I'm writing this email and a Netscape 3.0 browser window.
The following is a long, fairly detailed description of what you probably
need to do to set up Connection 3000 to use both the ethernet and dial PPP
connections simultaneously. I'm responding to the list because this is a
question I've answered privately a few times and hope the details which
follow will be of use to others.
I believe that WRQ Connection 3000 version 6.0 is the current version,
with WRQ Reflection 1 version 5.2 being the current terminal emulator.
At any rate, those are the versions I'm using with Windows 95. One word
of warning. The software is installation order sensitive. Install
Connectin 3000 first, then Reflection 1, then Netscape.
When the software has been installed, you will need to make some
configuration changes. Here we have a domain name server (DNS) but we
don't have the HP 3000's in it (for some unexplained security reasons).
We use a HOSTS file to tell Reflection and other networking software the
names and IP addresses of our devices (the HP 3000's, routers, etc.). I
think WRQ provides a sample HOSTS file, but if not, it is really simple.
On each line of the HOSTS file (which you can create with NOTEPAD) are
the IP address, the name of the system, and an alias for the system. So,
for a system with the IP address 192.xx.yy.zz which we call CDA9, the
entry looks like:
192.xx.yy.yy cda9 CDA9
Create the HOSTS file and place it in the WINDOWS directory.
Next, got to CONTROL PANNEL and launch NETWORK by double-clicking on it.
You should see a number of items in the box "The following network
components are installed:" Scroll down until you find the entry:
Reflection Network Protocols -> {name of your ethernet card}
Click on that line so that it is highlighted. Next, click on PROPERTIES.
The frame "Reflection Network Protocols Properties" should pop up. Mine
automatically displays the tab "TCP/IP". If this tab is not currently
displayed, click on it so that it is displayed.
You should see two lines in the "Interfaces" box:
Ethernet0 - {your ethernet card}
Serial0 - Reflection Serial Adapter (SLIP/PPP)
Put your PC's IP address in the "IP Address:" box if it is not already
there. Same for the "Subnet Mask:" box.
Click on the Ethernet0 line so that it is highlighted. Make sure that
the "Enable Interface" box is checked.
Next click on the Serial0 line so that it is highlighted. Make sure that
the "Enable Interface" box is checked. And now for a question. Does
your ISP assign IP addresses when you log in? If so, you need to thave
the "Enable Remote Configuration" box checked.
Click on the Ethernet0 line again. Next, click on the "DNR" button. You
should see the path to your HOSTS file displayed. Below the path are
some radio buttons. Click the button "Hosts File, then DNR". That way
your local systems will be accessed through the HOSTS file, and any
system you need to reach via your ISP will use DNR.
Now we come to the box "Domain Name Servers". There are two options here
and I've used both.
If your LAN *DOES NOT* have a Domain Name Server, then place the IP
address of your ISP's domain name server in the box. If your ISP has a
secondary domain name server, place its IP address in the second line of
the box (use the "Add" button to add the addresses).
If your LAN *DOES* have a Domain Name Sever, then do the following:
Place the IP address of your ISP's domain name server on the first
line in the Domain Name Servers box.
Place the IP address of your LAN's domain name server on the second
line in the Domain Name Servers box.
Place the names and IP addresses of all your local systems that you
frequently access in your HOSTS file.
There are pros and cons for this setup. If you have a complete HOSTS
file and keep it up to date, name resolution for your local (LAN/WAN)
systems will be fast, and name resolution for internet sites will be fast
(your ISP's domain name server will be checked before the local LAN
domain name server). However, systems which are on your local LAN/WAN
and not in your HOSTS file will take a while to access.
When the domain name servers have been added, click OK. The "Reflection
Network Protocols Properties" window should be displayed.
Next, what networks do you need to access through the ethernet0 interface
(LAN)? Some recommend using the "Gateways" box to configure in gateways,
but we haven't had much luck using it when there are both ethernet0 and
serial0 interfaces. Instead, we use static routes. To set up the static
routes you must know the destination addresses and the address of the
gateway you go through to reach those addresses.
Click on the "Static Routes" button. The "Static Route Table" window will
be displayed. Click on "Add" and enter the static route information.
Oh, and apparently Connect 3000 searches through the static routes in the
order in which you list them, so be careful of the order of entry. Below
is a listing of my entries (with addresses changed so they are not made
public).
Destination Subnet Mask Interface Gateway MTU Metric
192.10.0.0 255.255.0.0 Ethernet0 164.123.156.1 Default 0
198.22.0.0 255.255.0.0 Ethernet0 164.123.156.1 Default 0
198.23.0.0 255.255.0.0 Ethernet0 164.123.156.1 Default 0
Note that the "Interface" is "Ethernet0". If for some strange reason you
need to put in a static route for reaching a site through your ISP, you
would enter that route with Interface "Serial0".
When you have entered the static routes, click "OK" which will take you
back to the "Reflection Network Protocols Properties" screen.
I'm not a fan of Probe, so I disable it. To do so click on the "HP 3000"
tab, then in the Probe Options section click on the radio button "Do Not
Use Probe".
Next, click on the "NetBIOS" tab. In the "Name Resolution" section,
click on "Use DNR, then Broadcasts" if it is not already set (it is the
default).
If you have HPOPENVIEW or similar, configure your SNMP information by
clickin on the "SNMP" tab and entering your "System Name" (name of your
PC), your "Location" and your "Contact" (your name and phone number
typically), then make sure there is a check mark in the "Enable SNMP" box.
Usually Connect 3000 sets up the PPP/SLIP screen pretty well by itself.
To verify the settings it made, click on the "PPP/SLIP" tab. I don't
have the software save my passwords as I prefer to entere them each time
I log into my ISP, so my settings in the "Dialing" box are "Show Dialing
and Login" checked, "Dial on Demand" checked,"Dial at Network Startup"
UNCHECKED, and "Microsoft Client Login" UNCHECKED.
Click on "Configure Dialing" for more options. The "Dialing Options -
Serial0" screen appears. Most of these are personal preference items. I
have only one number I dial, so I don't have any of the items on this
screen checked.
When you are done with this screen, click "OK", and continue clicking
"OK" until you get to a point where Windows 95 asks you to reboot. Since
you need to reboot for the changes to take effect, click that option and
let the PC reboot.
What you should find is that through Reflection 1 you can reach any of
your local HP 3000 systems by using the names you entered in the HOSTS file.
If you have an intranet web server, you should be able to reach it via
Netscape, Internet Explorer, etc. by entering its name in the URL text
box (provided you put its name and IP address in your HOSTS file). If
you then want to go an internet site (like jazz.external.hp.comm), just
enter its URL and a dial dialog box will appear. Depending upon the
options you set, it may ask you to enter a phone number or select a phone
number from those it has on file. In my case I have that option turned
off so the dialer immediately starts dialing. I then get a login window
and a login prompt from my ISP's system. After the login is accepted,
the connect message appears followed by what look like garbage
characters. Press ALT-C and your connection is established. A few
seconds later your internet web page will start to appear.
A little telephone icon at the bottom right of the screen (task bar)
shows the status of the phone line - on hook or off hook. To disconnect
from your ISP, double-click on the telephone icon in the task bar and
then click on the "Disconnect" button.
It works very well and it is really nice to be able to be able to be
connected to intranet and internet sites at the same time.
Unlike the Windows 95 stack (which won't talk to classic systems and
wouldn't work with some of the odd-ball software we have), the WRQ stack
works with just about everything. It also won't load if it detects that
someone on your local LAN is using the IP address you have configured for
your PC, so there are fewer "duplicate IP address" problems.
If you need additional information, feel free to contact me directly.
John
--------------------------------------------------------------
John Korb email: [log in to unmask]
Innovative Software Solutions, Inc.
The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.
|
