OT Sco Unix question

[Brian K. White]

On 8/27/2011 8:32 AM, Del wrote:
> Hi:
>
> I am running Filepro on SCO 5.0.6.
> Recently I had to replace my router, and now SCO is not accessing the network.
> Can’t ping the router at all.
> Can’t ping the SCO box from my PC.
> I don’t know much about networking, but I guess this is because the new router (Cisco RVS-4000) is configured to allocate dynamic IP addresses, and SCO is not set up for that.  My old router somehow supported both dynamic and fixed IP, but I don’t think this one will do that.  The PC’s in my network are set up for dynamic IP allocation, but not SCO.  I am running Facetwin , but if TCP/IP is not working, it can do nothing.
> Can someone point me to the right resource/help file/documentation/forum to figure out how to configure SCO to accept a dynamic IP, or is this something that is best done by someone who really knows what they are doing?  The people who sold me my SCO box and set it up are long gone at this point, so I need help from somebody who really knows how, and, of course, I am willing to pay a reasonable fee for such help.
> Please reply off list.

Perhaps you should have had someone who does know even the very basics 
about networking to replace that router.

Whoever installed the new router should have looked at the old router 
and replicated it's config. If you did this yourself, now you know why 
you should have had your computer guy do it. If you computer guy did it, ...

Anyway no you can't make the unix box do dhcp (well, you can, it just 
wouldn't do you any good).

The safest, most correct, and simplest thing is to power up the old 
router and log into it (use a laptop or a pc disconnected from the 
network only connected to the old router) and copy down at least these 
settings:

* LAN IP & netmask
* DHCP Server address range
* DMZ and and other port-forwarding rules

And change the new router to match.
Reboot everything and you should be done.

Unless you changed other stuff to accommodate the new router like 
removing static ip's from printers and pc's. In that case then you get 
to go and re-do everything some computer guy did once that you un-did.

If you can't power up the old router, then you have to do some deducing 
and guessing and trial & error.

You can figure out what the routers LAN IP should be by looking at 
"netstat -rn" on the unix box.

# netstat -rn
Routing tables
Destination      Gateway            Flags    Refs      Use  Interface
default          10.0.0.1           UGS         4  7185265  net0
10               10.0.0.200         UC          1        0  net0
10.0.0.200       127.0.0.1          UGHS        2        0  lo0
127.0.0.1        127.0.0.1          UH          7    18192  lo0
224              10.0.0.200         UCS         0        0  net0
#

In this example, the router is 10.0.0.1

Next you can tell the netmask and at least the one address that should 
NOT be in the dhcp pool by looking at "ifoconfig -a" on the unix box:

# ifconfig -a
net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
         inet 10.0.0.200 netmask ffffff00 broadcast 10.0.0.255
         perf. params: recv size: 32768; send size: 32768; full-size 
frames: 1
         ether 00:03:47:31:12:46
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
         inet 127.0.0.1 netmask ff000000
         perf. params: recv size: 57344; send size: 57344; full-size 
frames: 1
atl0: flags=404a<BROADCAST,LOOPBACK,RUNNING,MULTICAST> mtu 8232
         inet 0.0.0.0 netmask ff000000
         perf. params: recv size: 4096; send size: 8192; full-size frames: 1
#

In this example, the unix box itself is 10.0.0.200 so the dhcp pool (the 
range of addresses the dhcp server will serve up) must NOT include this 
address.

In this example the netmask is "ffffff00" which is just another way of 
saying "255.255.255.0". Yours may possibly be different but it's unlikely.

This means, if the unix box is configured as 192.168.0.10 and it expect 
the gateway (router lan ip) to be 192.168.0.1, then on the router you 
change the lan ip to 192.168.0.1. Then on the router find the dhcp 
settings and change it so that the starting or lowest IP is any address 
above 192.168.0.10 . Typically you don't say 192.168.0.11 in this case. 
It depends on how may pc's and other objects you have but one reasonable 
config just for example might be to set the dhcp server to start at 
192.168.0.101 and end at 192.168.0.254 (255 is the broadcast address in 
this example and there are no more addresses in the network in this 
example) This lets up to 153 pc's and other devices connect at the same 
time and all get their adresses automatically and allows up to 99 
fixed-ip devices to exist on the same network without the automatic ones 
ever conflicting with the static ones, as long as all the static devices 
have addresses from 192.168.0.2 to 192.168.0.100.

Getting this info from the unix box isn't really good enough though 
because the unix box doesn't actually know everything. This will only 
tell you enough to make the unix box work, but other stuff may still 
have problems.

For example(s):

If you are sharing printers from PC's and the unix box is printing to 
them via facetwin, (not by ansi passthrough-print but by configuring 
facetwin printers in the spooler) then those PC's should all have static 
IP's or else those printers will stop working every once in a while.

If you have any network printers that you want the unix box to print to, 
they should all have static IP's.

There are other things that might need to be static on any network but 
printers and pc's sharing printers are the most common. If you have a 
windows server and it's acting as a local dns server then that needs to 
have a static ip for example. If you have any automated file transfer 
jobs going to/from a pc or windows server then they may or may not be 
reliable without static ip's.

The simplest way to make sure you get everything without having to know 
everything, is just copy the old routers settings since presumably the 
old router was working correctly.

Otherwise you have to go find out everything on your network. Are there 
any printers? Do you need the unix box to be able to print to them?
Most printers have a button or menu choice to print out a setup sheet 
that shows all their settings, and it will show you if it has a static 
IP and what that IP is, or if it's set for dhcp (automatic dynamic ip).
In the case of non-network printers connected to print servers, at least 
for HP's the print server has a button that prints the print server 
settings. Go around and find all the printers static IP's and adjust the 
dhcp start/stop address range in the router so that none of those static 
IP's falls within that range.

If you have printers that used to have static IP's but now they're 
dynamic then you have to get the printers old ip's from the unix box 
print spooler configs and put them back. But there are several different 
ways to print from the unix box and several different possible places to 
locate the info about ip addresses or hostnames the unix box is 
expecting those printers to be at. That's completely impractical to get 
into here without knowing if you even have any such printers to worry 
about, let alone which of the literally countless ways they might be 
accessed by the unix box.

I mentioned port-forwarding and DMZ but never elaborated. That is for 
accessing the unix box from the internet. If you weren't doing that 
before and don't want to now either, and don't have anything else on 
your network that you want to access from outside like security cameras 
or a windows server or mail server etc, then don't worry about that.

You can facetwin from home or anywhere else by port-forwarding tcp port 
7013 to the unix box lan ip and adjusting one of the settings in 
facetwin.cfg
ignore_pc_ip_address_for_password_crypt=YES
Unless your facetwin is very very old on the server. Even if it is it's 
a free and easy upgrade to the latest.

Next time maybe consider that a router is not a toaster.

-- 
bkw