RE: FPNW Windows 2003 SBS Netware 4.2



John,

I have been through this with SBS before, but first off I need to clarify a
few things.
Firstly, when you say you want the Novell Clients to see SBS as a Novell
server do you mean that you want the clients to be able access resources such
as data, network shares etc?
If so the only way I could get it to successfully work was to install the
Microsoft Client for Novell networks. This is not the client that comes as
part of your OS. It is a separate install / download from Microsoft. I can't
remember the exact download location but I found it by browsing Microsofts
documentation on Migration from Novell Groupwise to Windows 2003. The client
will need to be installed on the clients. I don't recommend installing it on
SBS though as it caused intermittent loss of network connectivity leaving me
no choice but to reinstall the NICS and re-run the Internet config wizard
Secondly I assume that you are running a Novell Server? Are you running
groupwise?
You will need to ensure that the clients run the Workstation (full install)
of Groupwise as opposed to the network install. Otherwise you will run into
Groupwise API problems.

I would suggest that before installing the client that you uninstall the
Novell Logon Client.

Unlike the Novell client which allows preconfig of such items as Logon
Scripts etc you will need to do this through AD profiles or login script
placed in the startup menu.

There are some other nitty grittys but this should point you in the right
direction

Not sure if this helps, but good luck..

Steve



"John Dvorchak Jr." wrote:

> Trying to get my Novell Clients to see our Windows 2003 SBS as a Novell
> Server. Have loaded FPNW with SP2, all configured ok, Internal and External
> Netwok numbers, login scripts and User folders. Logged in once or twice
> but then get disconnected from Server and can no longer access Windows 2003
> Server. Have tried IPX only (locks up Server on reboot) and IPX and TCPIP.
> This is not connected to our Novell Network at this time. Users exist and
> look ok, tried with and without passwords. The clients are a Windows 2000
> Professional and Windows XP Workstation, which by the way need the Frame type
> and External Netwok numbe manualy entered or they will not see the Server at
> all. Any help would be greatly appreciated. We need the Windows Server to
> migrate to a Windows only SQL program.
>
.



Relevant Pages

  • Re: Users Cant Access Documents on Server
    ... my computer to the network on the server. ... Connection Wizard none of the computers were listed. ... The Mac clients can not communicate with the server box. ... > Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot join Windows 2003 Server to SBS 2000 Domain
    ... this on all client computers at this remote office. ... All the clients but one at the main office are Windows XP Pro. ... > 'adprep' commands on the SBS 2000 server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Users Cant Access Documents on Server
    ... > then add my computer to the network on the server. ... Did you not see the computers in the Server Management taskpad section? ... The Mac clients can not communicate with the server box. ... >> Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy Results Wizard
    ... I guess we can rule out Windows ... If you can't reach the WMI from the server you will want to try to reach it ... switching off the Windows Firewall on one of the clients, ... Business Server Windows Firewall" (not Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • RE: Connection problem with 98 station on 2003 AD domain
    ... Thanks for your response and give me a right direction. ... I think the root cause is that those 98 clients do not have SMB ... packet signing enabled and cannot authenticate to a Windows Server 2003 ... How to enable Windows 98/ME/NT clients to logon to Windows 2003 based ...
    (microsoft.public.windows.server.migration)