HP3000-L Archives

May 2002, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jerry Leslie <[log in to unmask]>
Reply To:
Jerry Leslie <[log in to unmask]>
Date:
Thu, 30 May 2002 08:46:51 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Mark Wonsil ([log in to unmask]) wrote:
: Tom,
:
: FWIW, I have never had the patience to get a LinkSys router to work with
: static IP addresses.  Even the LinkSys documentation says it's tricky.
: Unless you have a really good reason for fixed addresses, let the router
: issue them.  If you set the lease days long enough, they will rarely change
: in a small network like that.  Do you plan to use any port-forwarding
: features?
:
: Mark
:
Tom, disregards my previous post.

The Linksys router defaults to 192.168.1.1 Its DHCP IP address range
defaults to 192.168.1.100 through 192.168.1.149.

So addresses 192.168.1.2 though 192.168.1.99 are available as static IPs.

My VAXStation's IP  is 192.168.1.96, one Windows 98SE PC's IP is
192.168.1.90, because it runs a LPD server package the VAXStation
prints to. The second Windows 98SE PC is set up as a DHCP client,
which means its IP address is 192.168.1.100.

On Tom's LAN, all PCs, print servers, H-P 3000s should all have the same
netmask; e.g. 255.255.255.0.

I do have some ports forwarded to my VAXStation so it can be reached
from the internet.


--Jerry Leslie   [log in to unmask]  (my opinions are strictly my own)
  Note: [log in to unmask] is invalid for email

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2