cant login on new install
rbarr8
unable to login. I have run DSREPAIR several times and each time I get
ERROR: Adding a Network Address Property. I have just installed a newly
downloaded "Novell Client for Windows" on my new machine running Windows XP
Professional. I also just got my server up and running so I am at square
one and completely lost. Please help a frustrated novice.
Thanks, Roger
Donald Albury
wrote:
TID 10063799
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10063799.htm)
may be what you need. Did you install the server IP-only, or IP and
IPX? Did you install the client IP-only, or IP and IPX (the default)?
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses
rbarr8
How can I tell what choice I made on each?
Thanks, Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>I am not sure how I configured the protocol on either the server or the WS.
>How can I tell what choice I made on each?
At the server console, enter M TCPIP. If you get listings for
TCPIP.NLM and TCPIP.MPM, you have IP bound and loaded. At the server
console enter M IPXSPX. It you get listings for IPXSPX.NLM and
IPXSPX>MPM. you have IPX bound and loaded.
For the client, right click on the red N in the system tray, and look
in the Protocol Preferences page. The Protocol field will show you
whether IP, IPX, or both was/were installed with the client.
rbarr8
TCPIP.NLM and IPXSPX.NLM but neither of the TCPIP.MPM or IPXSPX.MPM were
there. On the WS, I show the IP protocol only.
Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>I ran the two strings as you suggested for the server and it shows the
>TCPIP.NLM and IPXSPX.NLM but neither of the TCPIP.MPM or IPXSPX.MPM were
>there.
Let's not worry about the MPMs for now.
>On the WS, I show the IP protocol only.
Let's go back to baiscs, I may have been distracted by the DSRepair
error you reported. When you try to login, click on the Advanced
button, and see what is in the Tree, Context and Server fields, report
that back here. Then , clear the Server field, and enter the server's
IP address there, and see if you can log in.
rbarr8
and then configure and then advanced and then network address and hard coded
the server ip address. I was then able to log in. I also followed your
procedure and changed the server information to the server IP address and
that worked also. So now I am to the point that I can login, however my
server shows an abbend on boot that refers to the network address. On the
WS, my tree is ROBERT_MARINO_TREE
my context is .ROBERT_MARINO
my server is
ROBERT_MARINO_SRV
then the prompt I get is ROBERT_MARINO_SRV <1>
So I really feel we are making good progress
Thanks, Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>Donald, I did go in to the properties of my WS local area network connection
>and then configure and then advanced and then network address and hard coded
>the server ip address. I was then able to log in.
Configuring SLP will probably fix this. After you get the server
abend resolved (see below), take a look at TID 10062474
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10062474.htm).
Post any questions about it back here, and we'll help you.
>I also followed your
>procedure and changed the server information to the server IP address and
>that worked also. So now I am to the point that I can login, however my
>server shows an abbend on boot that refers to the network address. On the
>WS, my tree is ROBERT_MARINO_TREE
> my context is .ROBERT_MARINO
> my server is
>ROBERT_MARINO_SRV
>
>then the prompt I get is ROBERT_MARINO_SRV <1>
Post the contects of the abend.log file from the server in the
novell.support.os.server.netware5x.abends-halts forum.
rbarr8
no longer get the abend. When I restored the image, it configured itself
for the on board lan in the motherboard and I have now installed XP
professional on the WS and can no longer log in. So you see I moved forward
several steps and backed up enough to still be asking for help.
Thanks, Roger
"Donald Albury" <dalbury@not_bellsout.net> wrote in message
news:03cv00l40l357u29g...@4ax.com...
Donald Albury
wrote:
>I have now rebuilt my system and restored an image of the working server and
>no longer get the abend. When I restored the image, it configured itself
>for the on board lan in the motherboard and I have now installed XP
>professional on the WS and can no longer log in. So you see I moved forward
>several steps and backed up enough to still be asking for help.
Can you log in if you put the IP address of the server in the Server
field under the Advanced button of the client?
rbarr8
When the server came up it auto configured the lan with several TCP/IP
protocols but none was IP. I rem out the IPX line and added an IP line with
the 192.168.0.2 address line with a mask of 255.255.255.0. and all seems ok
now. I am not sure I understand the whys and hows of the address scheme,
however it does work. My next step is to eliminate the the turnover cable
between the server and the WS and connect each to my router.
Thanks, Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>I can log in now that I hard coded the IP address 192.168.0.3 in the WS.
>When the server came up it auto configured the lan with several TCP/IP
>protocols but none was IP
I don't understand this. 'IP' as we usually use it in the forums is
just short for 'TCP/IP'. What other 'TCP/IP' protocols were auto
configured?
>I rem out the IPX line
No need to do this, as both protocols can run on the server.
>and added an IP line with
>the 192.168.0.2 address line with a mask of 255.255.255.0.
But you used 192.168.0.3 as the server IP address in the workstation
client. Are we talking about the same server?
>and all seems ok
>now. I am not sure I understand the whys and hows of the address scheme,
>however it does work. My next step is to eliminate the the turnover cable
>between the server and the WS and connect each to my router.
You will need to configure SLP, which takes us back to TID 10062474
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10062474.htm).
Donald Albury
wrote:
>Hi Donald, My terminology may have confused the issue. When I had a
>separate PCI LAN card, I manually configured the address as 192.168.1.1 and
>checked the IP box during the configuration. Now with the on board LAN and
>letting the system auto configure, I saw and IPX address, 802.2 and 802.3
>and ETHERNET_SNAP and ETHERNET_II. The ETHERNET_II had some weird (to me)
>address and the IPX protocol. I rem out the IPX line and replaced it with
>my IP line changing the address to 192.168.0.2 as I had on the original
>server. After your last message I put the original IPX line back in and
>left the address it originally had. I am attaching the config.txt file and
>the current modified autoexec.ncf file. Hope that clarifies my muttle.
First, I highly recommend that you make all changes to network loads
and binds by using INETCFG.
From your autoexec.ncf:
ServerID F3139D7
LOAD TCPIP
LOAD ODINEB.NLM
rem LOAD LNE100TX.LAN SLOT=4 FRAME=Ethernet_II NAME=LNE100TX_1_EII
rem BIND IP LNE100TX_1_EII addr=192.168.1.2 mask=255.255.255.0
rem LOAD LNE100TX.LAN SLOT=4 FRAME=Ethernet_802.2 NAME=LNE100TX_1_E82
rem BIND IPX LNE100TX_1_E82 network=00000001
You've remmed out all the network card loads and binds. I don't see
how your server can communicate.
Ethernet_II is the frame type used by TCP/IP. You can also configure
SPX/IPX to use Ethernet_II as its frame type, although 802.2 is the
traditional default for SPX/IPX. You do not need 802.3 or SNAP.
This is the comparable portion of autoexec.ncf on my home server:
; Network driver LOADs and BINDs are initiated via
; INITSYS.NCF. The actual LOAD and BIND commands
; are contained in INITSYS.NCF and NETINFO.CFG.
; These files are in SYS:ETC.
sys:etc\initsys.ncf
#LOAD TCPIP
#LOAD CE100B.LAN SLOT=10003 FRAME=ETHERNET_II NAME=CE100B_1_EII
#BIND IP CE100B_1_EII addr=192.168.1.20 mask=255.255.255.0
gate=192.168.1.1
I have loaded INETCFG at the server console, and let it transfer the
network loads and binds to initsys.ncf. I installed the server
IP-only, so only the loads and binds required for TCP/IP were created.
Again, I recommend that you load INETCFG and use it to get your
network settings fixed.
rbarr8
the LNE100TX lan cards. I now have a motherboard with an onboard realtek
lan chipset. After taking the defaults as the server booted up on the new
motherboard, I tried to replicate what I saw from the old LNE100TX settings.
They appear at the end of the autoexec.ncf file. I am able to log in to the
network now but do not understand the signifcance of the addresses I used.
I replicated the address that was associated with the old lan cards
192.168.0.2 for the server and I hard coded the address 192.168.0.3 on the
WS. Where did these addresses come from? and if I add additional WS's,
what addresses do I set them up for? The above configuration is for 1
SERVER and 1 WS connected with a xover cable. I will be adding a router to
the mix and need to know any differences in the way additional addresses
will be handled.
Thanks, Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>I remmed out all the network card loads and binds because I no longer use
>the LNE100TX lan cards. I now have a motherboard with an onboard realtek
>lan chipset. After taking the defaults as the server booted up on the new
>motherboard, I tried to replicate what I saw from the old LNE100TX settings.
>They appear at the end of the autoexec.ncf file. I am able to log in to the
>network now but do not understand the signifcance of the addresses I used.
>I replicated the address that was associated with the old lan cards
>192.168.0.2 for the server and I hard coded the address 192.168.0.3 on the
>WS. Where did these addresses come from? and if I add additional WS's,
>what addresses do I set them up for? The above configuration is for 1
>SERVER and 1 WS connected with a xover cable. I will be adding a router to
>the mix and need to know any differences in the way additional addresses
>will be handled.
Move the lines
LOAD RTSSRV SLOT=5 FRAME=ethernet_II NAME=RTSSRV_1_EII
BIND IP RTSSRV_1_EII ADDR=192.168.0.2 MASK=255.255.255.0
to just after
LOAD TCPIP
LOAD ODINEB.NLM
in the autoexec.ncf file.
Delete the lines
LOAD RTSSRV SLOT=5 FRAME=ethernet_802.2 NAME=RTSSRV_1_E82
BIND IPX RTSSRV_1_E82 NET=D8218A47
LOAD RTSSRV SLOT=5 FRAME=ethernet_802.3 NAME=RTSSRV_1_E83
BIND IPX RTSSRV_1_E83 NET=912EF217
LOAD RTSSRV SLOT=5 FRAME=ethernet_snap NAME=RTSSRV_1_ESP
BIND IPX RTSSRV_1_ESP NET=F55CD7AE
and
BIND IPX RTSSRV_1_EII NET=48E97843
from autoexec.ncf.
If you want to use IPX on the server (inaddition to IP), load INETCFG,
and add IPX there.
If you have only a few workstation, you can manually assign an IP
address to each one. For a simple LAN (one physical segment), all IP
address should be in the same range, in your case, 192.168.0.xxx.
With more workstations, you should set up a DHCP server. You can use
the DHCP server in NetWare, or from a Windows or Unix/LInux box. Your
NetWare server should always have a static IP address, however. If
you wnat to run DHCP on the NetWare server, see the docs, and ask
questions in the novell.support.os.server.dns-dhcp forum.
Adding a router implies you will have more than one physical segments,
usually at different location. Each location needs to have its own IP
address sub-range, i.e., 192.168.0.xxx at location A, 192.168.1.xxx at
location B, etc. If you are adding a router to just give access to
the Internet, however, you will need a firewall server to provide NAT
(Network Address Translation) and protect your LAN. You can use
BorderManager (http://www.novell.com/products/bordermanager/) for
rhis.
rbarr8
I appreciate very much the info on the addressing scheme. We have one
SERVER and 10 WS's all at one office and I think a 10 port switch common to
them all. I know we have a router off one of the legs of the switch for
access to the internet and I thought it as a DHCP assigned the addresses for
the entire network. (how can I find out if the addresses are being assigned
by the router?) We do have a static IP address from BellSouth. What I am
working with here at my home is a replica of the network at the office and
when I have a better understanding and get it to completely replicate the
office, I will replace the office server with this one. I initially had
scsi drives in my "MOCK" server but ran in to all kinds of trouble so I have
moved back to IDE drives like the office and now have them working. I am
attempting to move in very small steps to get the MOCK server ready to
replace the office SERVER. You have been very helpful toward that end.
Thanks, Roger
"rbarr8" <rba...@bellsouth.net> wrote in message
news:RKgOb.308$P5....@prv-forum2.provo.novell.com...
Donald Albury
wrote:
>Donald, I made the changes you suggested and all appears to be working fine.
I'm glad to hear that.
>I appreciate very much the info on the addressing scheme. We have one
>SERVER and 10 WS's all at one office and I think a 10 port switch common to
>them all. I know we have a router off one of the legs of the switch for
>access to the internet and I thought it as a DHCP assigned the addresses for
>the entire network. (how can I find out if the addresses are being assigned
>by the router?) We do have a static IP address from BellSouth. What I am
>working with here at my home is a replica of the network at the office and
>when I have a better understanding and get it to completely replicate the
>office, I will replace the office server with this one. I initially had
>scsi drives in my "MOCK" server but ran in to all kinds of trouble so I have
>moved back to IDE drives like the office and now have them working. I am
>attempting to move in very small steps to get the MOCK server ready to
>replace the office SERVER. You have been very helpful toward that end.
I assume you have a DSL line from BellSouth. I have that at home. I
use a D-Link DSL router behind the Alcartel DSL modem, and the D-Link
provides my DHCP on my home network. Even for a 10-user office setup,
I think you should have a firewall server and a DHCP server (they can
be the same box). If you have configured Windows to get an IP address
automatically, then it will use DHCP. You can check the status of the
IP address by entering 'winipcfg' (on Win 9x/ME) or 'ipconfig' (on Win
NT/2K/XP) in a DOS box.
I have an IDE drive in my home NW server, but I think most of the
SysOps will tell to use SCSI in a production environment.