configuring multiple routes in Novell Netware 6

Hi all,

We have performed subnetting through VLAN in our entire LAN.Our network is in the range of -
Different subnets that we have created are :,,
All our servers like LINUX,CITRIX,WINDOWS,NOVELL,DNS server are connected in 0.0/22 network.
All our clients are in 4.0 and 8.0 networks.

Our aim is to make all servers get routed to all networks.We r using Netgear FSM7328S L3 switch and made all the configurations,also kept all the networks in routing table of CITRIX,LINUX through some commands and all the clients r able to access well.

Problem is with Novell server,in which i am not able to get how to configure the routes,i have only added one default gateway : (ACTIVE)
All our clients r running windows 98,2000,xp systems,in the 4.0 network machines,i have given 4.1 as the default gateway and in 8.0 network machines,i have given 8.1 as the default gateway.All the clients are able to access all the servers,but not Novell(able to ping the IP but not name).In DNS server we have addes all the clients.

But after giving the Novell server IP and name in HOSTS file of each client,they r able to access that too only some machines not all though they r able to ping the name of novell server.

One more issue is, in Novell server itself is we r having pure DOS,so clients who want to work in pure DOS r not able to access LAN directory.

I think there is some configuration problem in server.....somebody please help me.

Thanks in advance.

Who is Participating?
I think the problem may be that you're using an IANA-reserved class C network scheme but exceeding the subnet mask of class C, so you're really not subnetting.  To do what you want, you should have used class B or class A private ranges with your mask.  Not that you shouldn't be able to supernet your class C like you did, but it's like using a laser-guided missile to swat a fly - way overkill, and more complex than necessary ;)

As I said before, you're really not subnetting, you're supernetting.  NetWare has, historically, had difficulties with routing and supernetting, because - well, frankly, because nobody cared about supernetting in a private LAN.

a couple of TIDs I have found relevant to this, and your problem, is:

Not knowing what SP level of NetWare 6.0 you're using, or what version of TCPIP.NLM you're running, makes it tougher to be more specific, as there may have been supernetting enhancements and fixes in newer versions of NetWare's IP stack.  

This is the current (last?) TCPIP update for NetWare 6.0: 
It requires NW6.0SP1 minimum.  Don't know if any TCPIP updates for NW6 resolve the supernetted routing issue.

Essentially, to fix this while sticking with your supernet scheme, you have to set up the NetWare server as an end node, without routing.  In theory. ;)
Setting up static routes in Netware is easy. Quickest way is from the console using INETCFG

Load that, then open Protocols, TCP/IP, LAN Static Routing Table, then Insert, and add your new route (Network, Subnet Mask, Next Hop).
TCPCON does what you need.

Load it from the console follow the detailed help screens.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

haribabupanchireddyAuthor Commented:
I have tried all the steps that i can using INETCFG and TCPCON....but still i am not able to route the things properly.

The only configuration that i have made now is...default route:,with this i am able to ping the novell server IP from other clients of other network but not its name,so i have added its name&IP in each of the clients hosts file,then they are able to access the server but they r not able to access the server in pure DOS mode.

I think there is some mistake in the server configuration...If anybody provide ur contact number,my sys admin will talk....Its urgent for me.

Thanks all.
Looks to me more like supernetting, since you took class C up into the class B range...

Also, Novell is a company that sells several OSes, one of which is NetWare.  Assuming that's what you mean by "novell," that's what you should call it.  Calling NetWare "Novell" perpetuates the myth that everything from Novell is, or requires, NetWare, which couldn't be further from the truth.

That said, regarding the DOS clients, IP and DOS is dicey to begin with; unless you get your routing fixed, you're just going to frustrate yourself.

Assuming that the IP addresses you specified are on a router, the default route on the NetWare box should be the router, as you apparently have done, but you should also have static routes set up to ensure the return packets go to the right place.  For some reason, static routes work best when connecting to subnets other than the one the server resides in.

To set up static routes to all subnets on the NetWare server, you specify each of the networks on its own route, type network, with a next-hop of the router.  Since the servers are al on the 0.0 subnet, you should have one entry for the network, next hop, and one for the network, next hop  The routes between the networks should be on the router, so if your clients have a default route of, the router should handle calls to the 0.0 network routing them through the 0.6 interface and the same for the 8.0 network.  Since it works for the other servers, I assume that is so, so that means default route is inadequate and you need to set up the static routes on the NetWare box.

If you're unsure how to set up static routes using INETCFG let us know.

Further, the netgear box (assuming that's what you're using as a router) may be blocking multicast.  If so, you're probably breaking SLP besides.  Since PING works even when SLP is broken, that's not likely the issue, but it's something you want to watch for.  It may be necessary to add the SLP DA to all the clients, in Properties, Service Location tab.   If the Netgear box is also your DHCP, you probably don't have the ability to specify SLP info via DHCP as it should be.

If the NetWare server is in DNS, and the clients use that DNS server for other name resolution, then they should be able to PING by name without having HOSTS file entries.
haribabupanchireddyAuthor Commented:
Hello Mr.ShineOn,

  2-Select> PROTOCOLS
  3-Select> TCPIP
  4-Select> Static Routing
  5- Select> Enabled
  6- Select> Static Routing Table: <enter>
  7-<insert> to bring up the Static Route Configuration
  8-Select> "Route to Network or Host" (I have selected network)
  9-Select> Either  "Network" or "Host"<enter>
 10-Select> "IP Address of Network/Host" and enter the proper address(I have given
 11-If configuring a route to a network Select> "SubNetwork Mask" and enter the proper mask(I have given
 12-Select> "Next Hop Router On Route"(I have given
 13-Updated the database
 14-Reinitialised the system

But the route has not been added in the TCPCON>IP routing table.
Then i have reboot my server,then also the route has not added.
I have tried many times.

Then i tried to add dynamic default route as follows:

    Select ---> IP ROUTING TABLE
        Select ---> PROCEED: <ENTER> WHEN DONE
            <INSERT> to bring up a new IP ROUTE INFORMATION table.
In this at the destination tab i have given...
          at the mask..... its showing the message ..."The subnetmask is less then the subnetmask")

Thus,i am unable to add dynamic route also which is a temporary one.

Here i am Placing all the existing settings in our server step by step:
2.TCP/IP Static routes:
                                  Destination                 Next hop
                              Default route 0      
3.IPX protocol configuration:
                                  IPX status    -   enabled
                     packet forwarding     -   enabled
                   routing protocol          -  RIP/SAP only
           Tunnel IPX through IP         -  disabled
           Mobile IPX through IP         -  disabled
           Address mapping gateway  -  disabled

4.Bindings :
                Protocol              Int/group              status              Identifier
                   IPx                   B57_1                enabled                 -
                   IPx                   B57_1                enabled                 -
                   IPx                   B57_1                enabled                 -
                   IPx                   B57_1                enabled              321984DB
                  TCP/IP               B57_1               enabled    

5.Manage configuration:
                                    SNMP parameters....(all r default settings)
6.Network interfaces:
                               Board name            Interface          Group           Media            Status
                                  B57_1                  B57_1               -                ethernet         enabled
7.Configuration summary:
                               Board interface            TCP/IP               IPX                     Source  Route  Bri  ODINEB.N
                                    B57_1                 Ethernet-2        Ethernet_802.3           -                       -
                                                                    --              Ethernet_SNAP           -                        -
                                                                    --              Ethernet_2                 -                        -
                                                                    --              Ethernet_802.2           -                       -

Now,when i load as follows:

2.IP forwarded  :  disabled
3.SNMP access configuration:
                                        Transport protocol  -  local system
                                          community name -    public
4.IP protocol information:
                                  IP packet forwarding: End node (actually here another option is also present called ROUTER,in our server the option selected is ENDNODE)
5.IP routing table(2 routes):
                                 Destination         Nexthop                Type                Cost                 Interface
                                   default            remote                1                      3
                                   layer3               ESPL6                direct                   1                      3

NOTE:ESPL6 is the name of our netware server

6.Interfaces table:
                           Description                                              Address                       Interface               Type
                    Broadcom Netxtreme Gigabi                   00-0c076-82-3D-71                   1                    iso88023-csmacd
                    Broadcom Netxtreme Gigabi                   00-0c076-82-3D-71                   2                    iso88023-csmacd
                    Broadcom Netxtreme Gigabi                   00-0c076-82-3D-71                   3                    ethernet-csmacd
                    Broadcom Netxtreme Gigabi                   00-0c076-82-3D-71                   4                    iso88023-csmacd

From the above is there any mistake.
haribabupanchireddyAuthor Commented:
First let me clear one thing that whether our LAN is running under subnetting or supernetting?

I strongly believe that is subnetting.

Local addresses:Ina local network the Ip addresses that do not connect to the Internet will remain unique within the local network.An address range in each class is reserved for local networks that dont communicate with outside networks:

Class A: to –
Class –
Class C: to – is the range we choosed for our network and then implemented subnetting the mask to

Now i am worried with ur reply regarding supernetting.We r not using any IANA reserved addresses in our internal LAN,using only private class c address range.
You got that a bit wrong, it's:
Class A: to – 1 Subnet 8 bits to network number 24 bits for node numbers
Class – 16 subnets 172.16-31.0.0/16  16 bits to network number 16 bits for node numbers
Class C: to – 256 subnets 192.168.0-255.0/24  24 bits to network number 8 bits for node numbers
haribabupanchireddyAuthor Commented:
Yes,now i understood where i have done mistake.

That means i have implemented Supernetting instead of subnetting.Actually we want to implement subnetting inorder to reduce broadcasting and increase the performance of LAN.But,if what i did is supernetting,will there be any negative effect on LAN?Can i gain performance improvement with this?

Should we face any problems in future with this?Because now it is not possible to change into me.

In computing Everything is possible.
IMHO - Change to subnetting, such usage is not a common addressing implementation and sometimes it is not taken into account by programmers.

Read ShineOn's last message again, this is your situation.

haribabupanchireddyAuthor Commented:
My problem is that we r having a server on which Green Hills Software is installed and according to license conditions we should not change that servers IP address or subnetmask and also there are nearly 12 servers.So now it is difficult for us to change the network as it will effect all the clients.

So i want to know whether supernetting will cause any problem to the network (other than Netware server).Beacuse after 6 months we will remove Netware and migrate to Citrix.

Also,at present we r not using any SP on Netware 6 server,within one week we will be installing it sufficient?

Also,our staff is nearly 400 and we want to divide our whole network into small networks.
haribabupanchireddyAuthor Commented:
Yes,our present network configuration is wrong,with class c : can have only 4 different subnets,but here in LAN i made nearly 12 subnets(i dont know how they r working though my configuration is wrong??other than Netware)

Now we r thinking to implement supernetting with class C network: can make 62 subnets according to future requirements.

And today i will try Netware testing with this changed range.Before that i want to know again that,will there be any problems maintaining supernetting in our LAN(ignore Netware) interms of performance?

Performance-wise, not really.  

Now, you say the address and subnet mask of this Green Hills Software must not change - you mean it was installed with a subnet mask, and both the address AND mask must not change?  Nasty license agreement, there.  If anything *should* be changeable, it's IP and netmask.  Are you sure it's not just a matter of re-registering?  Also, if you supernet with /18 instead of /22 your netmask will have to change anyway, on these Green Hills servers.

If it's just the address and not the mask, you could easily switch to a straight, routed multi-network class C environment and keep the IP addresses, just change all the masks to  If your supernet changes from to netmask, your Green Hills software will have to have its netmask changed anyway, so why not go straight Class C?  Then, it's a simple matter of routing between class C networks, which NetWare (and anyone else that deals with IP) handles just fine, and you could have 254 different networks, each with 254 hosts, giving you up to 64,596 host addresses.  I say 254 networks because I dislike using network 0, and network 255 is reserved for broadcast, and 254 hosts because device 0 and 255 are normally reserved for network and broadcast respectively.  You could have 255 networks if you include network 0 through 254.  Just consider each Class C network as a "subnet" if your PHB's need to know you've got multiple subnets.

If you must do supernetting, you're going to have to 1) set your NetWare as an end-node and 2) recognize that other software may not like supernetting, and you just haven't discovered that yet, and 3) recognize that almost all IP-aware software knows that 192.168.x.x is a class C private network and will default the netmask to, adding another twist to troubleshooting when software or hardware is added, changed or updated.
Also, changing the netmask from to won't give you more "subnets" - it'll give you more hosts per supernet.  Instead of the current 1016 hosts per supernet you have with CIDR /22, you'd have 16,256 hosts per supernet with CIDR /18.  

The first supernet with CIDR /22 would be in the range of to, the second to and so on, giving you roughly 64 networks of 1,016 hosts, while CIDR /18 would have supernets of to, to, to and to - or actually only 4 supernets of 16,256 hosts each.
"... remove NetWare and migrate to Citrix... "

Non-sequitur.  NetWare and Citrix are not equivalent products.  Citrix is an enhancement on top of Windoze Terminal Server, while NetWare is a NOS.  Citrix has no directory service, and its file-and-print capabilities and other network services are limited by Windoze, and the fact that it's a thin-client environment.  NetWare and Windoze-cum-Citrix work quite nicely together, besides.
haribabupanchireddyAuthor Commented:
Subnetting Details
Creating 64 subnets from
                                                  Network                   Range of Hosts                      Broadcast
                                                   --                                      ----                                ---
                                                  ---                                      ----                                ---

Thus,i want to assign as the subnetmask to our entire network.

Last night,i have implemented this,now i am able to see the route added in the routing table and kept the Netware in route mode but not in end node.

I am able to ping the name of the client which is in other network( from Netware server,similarly from client i am able to ping thename of Netware server,but i am not able to access the data of the server,then again i placed the Netware server in clients hosts file then it worked(although for name resolution we r using DNS on Linux server),but now also i am not able to access the Netware through pure DOS from client.

At present there is no service pack installed,is this the problem ?

NetWare 6.0 with no SP?  Definitely a potential source of problems, but the source of the problem accessing NetWare from a DOS client?  Don't know.

What DOS client are you running?  If you're using IP it has to be either a late release of the VLM client or the DOS/WIN Client32.  Or are you talking about a Windows client and saying "DOS" to describe something other than the MS-DOS/PC-DOS/DR-DOS/FREEDOS Operating System?  Like, maybe you mean IPX/SPX?

The last SP for NetWare 6.0 was SP5, released in July, 2004, and there were several post-SP5 patches released in the intervening 2 years.   NW6.0SP0 was kinda buggy; I'm surprised you haven't been experiencing problems all along.
Also, et. al. are standard Class C private networks, not subnets off of  192.168.0 through 192.168.255 are reserved, non-Internet-routable Class C private networks.

The private networks are as dotENG described in his comment {http:#17182228}, with CIDR of class a =/8, class b=/16 and class c=/24

Is this some sort of layer-3 RCP/IP-only VLAN setup where you define your VLANs as subnets of a virtual IP network or something?  Is that why you keep talking about with "subnets?"

The VLANs I'm familiar with are layer 2, which can have "helper addresses" assigned to them to assist routing across VLANs, but if you're configuring an IP-only, purely IP-based VLAN, that could explain DOS clients not seeing the server, if the DOS clients are using IPX/SPX and not TCP/IP.  Excluding IPX/SPX from your VLAN setup, or not configuring IPX/SPX VLAN routing, will prevent IPX/SPX packets from getting from one VLAN segment to the other.
haribabupanchireddyAuthor Commented:

Yes,this is a Layer3 RIP VLAN setup.Each port is considered as different VLAN with different subnet.

Let us leave the DOS and Netware problem,tell me whether i can use the IP range as mentioned in my last reply and subnet amsk= or not?

Please give me reply as soon as possible.
Sure, is the natural netmask for private class C.  As long as your vlan device can be the supernet at /18, and your routes are set up on the switch, then nobody else that cares about that stuff even has to know.  Each vlan on each port has its own network (as it would in a subnetting situation) and the port's address is each vlan's default route, so you should be good to go, for IP anyway.

If you want to close this one out and open a fresh Q about the DOS and NetWare thing, that'd be OK by me.  If the /18 "lan" with /24 "vlans" works for everything but the DOS client thing, then you can establish what your environment is in the Question so we can directly address the DOS client issue without worrying about that.  Makes it easier to follow.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.