Connect to NOVELL Version 3.12 via IPX/SPX not LogOn / New Questio

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi KM,

thank You for your answer,
here my answer to that is what You ask:
--------------------------------_------
1. I working with Target Designer tool
and I have building the XPe image.

2. First I have building the XPe image,
with connect to server via TCP/IP,
its work fine. No problem.

3. I testet the NOVELL-Serve with my Notebook
(runs under Windows XP PRO), its works fine.
I testet with the same Username and the same
Password (as the XPe). Its works fine.

4. Next step was added "Client Services for NetWare"
with all other components (via Dependency Check)

5. In "Windows Logon (Standard)" I set the Settings:
"Enable Legal Notice before Winlogon:" OFF
"Show Friendly Winlogon:" OFF
"Show "Welcome to Windows" screen before Winlogon:" OFF

6. I build this System on the CF-Card, but the function is wrong:

The LogIn at the NOVELL is then however not successful.
In the network environment, the NOVELL-Server is visible,
but not eligibly.
In the registration of the preferred server in CSNW,
the error message comes always "access denied".
In the NOVELL-Server stands under
"Active Connections" NOT-LOGGEG-IN

--> IPX/SPX via Notebook is OK
--> IPX/SPX via Xpe not work! Why???

Please, what must I do?

Thank you very much in advance.
Jens Plambeck
 
I believe this is covered in one of Sean Liming's books:
http://www.seanliming.com/books.html , the service is probably failing to
start, here are several workarounds.

1) In TD, add a FBA Generic Command under the resources of the root
component with the following parameters: (Leave the other parameters set to
their default) Arguments: -v -l %17%\netnwlnk.inf -c p -I MS_NWIPX

FilePath: %11%\snetcfg.exe

Phase: 5600

or

2) At a command prompt on your runtime, you can run the
command:

snetcfg -v -l %windir%\inf\netnwlnk.inf -c p -I MS_NWIPX

or

3) Manually adding NWLink IPX/SPX/NetBios Compatible Transport
Protocol to your Local Area Connection Properties, under Network Properties
in your runtime.

After doing any of these, the service should startup on all subsequent
boots.
 
Hi Andy,

thank You for your answer,
I have tested Your workarounds no. 1 and no. 2,
but the function is furthermore wrong.

The problem is:
The LogIn at the NOVELL is then however not successful.
In the network environment, the NOVELL-Server is visible,
but not eligibly.



My question is:
---------------
I haves added "Client Services for NetWare"
with all other components (via Dependency Check).

How must I bind your workarounds at the same time?
Snetcfg is loaded also in the "Client Services for NetWare"!


Please, what must I do?

Thank you very much in advance.
Jens Plambeck
 
Sorry, to be clear, what i was getting at was to get you to ensure that the
protocol is binding to the nic, those steps I listed should accomplish this,
but based on your response i'm still not sure that's it's happening.

You need to verify this, if it's not bound, then you should try option 3 as
well. If it is bound then i'm not sure off the top of my head what the
issue, is perhaps there's another 'novell' or 'nwlink' component that needs
to be added. To be honest here, i'm not familiar with Novel software or
nwlink, so i'm not much help right now am i? <grin>

If this protocols are being bound to the nic and it's only an authentication
issue then this is probably more difficult. I do think the protocal is ok
since you can 'see' the server.

Please also search the archives of this newsgroup, search for novell,
nwlink, netware for any other hints in case someone else has had similar
issues.

--
Andy
--
Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top