Connectivity problem

[purus...@yahoo.com]

Dear sir,

I am having problem while connecting the Novell 3.11 server. It is visible
on back-bone machines. But it is not visible in other subnet Why? Even if
I give command display servers. It is showing the servers which are on
back-bone only. What should i do for other subnet.

Regards,

Purush

[Tim Scotland]

NW 3.x uses IPX to communicate with it's client. If you and your
workstation are on a different IP subnet, with a router that does not
route IPX then there is no way you can connect to it.

To confirm what is happening, ensure that you have IPX on your
workstation, and if it is bound, then you will need to get the config
of the router changed so that it will route IPX.

Tim

**********************
Scotland
God's Country
**********************
Volunteer SYSOP
No Direct Mail Please.

[Dave Lunn]

In addition to what Tim gave you, watch your frame type. 3.11 defaults to
802.3 so you need to match that too.
--
Dave Lunn
NSCV Sysop
http://support.novell.com

[purus...@yahoo.com]

Hello,

Server & clients are in same subnet.
I am having windows NT 4.0 gateway (router). Also IPX protocol is bound on
frame type 802.3 on router. IPX routing is enable on it. One more problem
is we are having Novell 4.11 in same subnet. When we up this server
(4.11), users are able to connect to Novell 3.11, but when Novell 4.11
goes down user are not able to connect to the Novell 3.11. It is giving
error message 'not able to find the server on network. Please check the
connectivity to the server'. So you might have clear the idea.

Please help me.

[purus...@yahoo.com]

In addition to the mail, In router we are having two network cards one on
back bone & other on perticular subnet. But i would like to ask you is
router come into the picture as novell server & clients are communication
through ipx.

[felton...@bigfoot.com]

Hi

Here is a document that may help:

http://tinyurl.com/h5y

Felton Green (SysOp)

[Tim Scotland]

It sounds like you have some kind of client problem. If you go to the
"Big red N" in the system tray, and right click on the client
properties, select the location profile, and then edit the default
profile. You will see that you default authenticator is set to NDS.
If you change this to bindery and fill in the details of the 3.12
server, you will be able to connect to the 3.12 server without any
problems.

However, you now may have problems connecting to the 4.11 server :-)

The difference is that the 4.11 uses a directory and the 3.12 server
uses a server based system (Like NT)

Let us know how you get on.

tim

**********************

[purus...@yahoo.com]

Dear Tim,

This could be the best solution, but the clients are connecting to Novell
3.11 through dos not from windows. I mean they boot the system in dos &
conntecting to the server. I would like to ask whether it will works after
changing the default to bindary???

[Tim Scotland]

The workstations boot to dos. Part of the boot process loads either
the dos Client32 or VLM's

If you are using VLM's you will find a net.cfg in the same folder as
the VLM modules. In this you will see a whole bunch of things listed
under dos requester.

Can you post this text so we can see what it has in it.

Tim

**********************

[purus...@yahoo.com]

Here is the net.cfg file. Please have a look of it.

------------------------------------------------------------------------
Link Driver 3C90X
FRAME Ethernet_802.3
FRAME Ethernet_802.2
;
; When using two or more adapters in a single machine, it is
necessary to
; specifiy which adapter should be used. The following two
parameters are
; used for this purpose:
;
; SLOT NN, where NN is the specific PCI BIOS identification
number of the
; 3C90X PCI adapter.
;
; BUS NN, Where NN is the Bus number.
;
; The next few lines specify the frame type. 3C90X.COM is a 4.10
DOS ODI
; driver. The default frame type is 802.2. To connect to a 3.11
server
; the frame type needs to be changed to 802.3. The following two
lines
; perform that change.
;
; This is the driver default
;
PROTOCOL IPX 0 ETHERNET_802.3 (binds IPX protocol to frame)
;
PROTOCOL IPX E0 ETHERNET_802.2
;
;
;
;
;
;(%VER NET.CFG - sample Netware DOS ODI configuration file V1.0)

NetWare DOS Requester
FIRST NETWORK DRIVE = F
;NETWARE PROTOCOL = NDS BIND
NETWARE PROTOCOL = BIND
preffered server = eis

[Dave Lunn]

Here's one I use to make my server boot up to talk to a PNW box.

Note the indents, they are critical and should be at least four spaces.

Link driver 3c90x
rem IRQ 11 leftover from an ISA NIC
rem PORT 300 leftover from an ISA NIC
FRAME Ethernet_802.2

Netware DOS Requester
PREFERRED WORKGROUP = te

FIRST NETWORK DRIVE = F

NETWARE PROTOCOL = PNW,BIND,NDS
SHOW DOTS = ON
USE DEFAULTS = ON
VLM = AUTO.VLM
VLM = NMR.VLM