p_borchert Absent Member.
Absent Member.
1918 views

Win10 no tree

Hello to anybody,

some time ago I installed win10 on a computer with XP. I can boot both. Now I want to add a Novell client. I tried some clients, but all I tried, did not show a tree. The last client I tried is the client for Win7.

So I looked what happens on the wire:

With XP there are two calls:

-------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------

With win10 there are 5 calls using different source-ports. One of them:


With XP I get the tree and can login. With Win10 there is no tree displayed and no login. On the wire there is no answer fron the Server. I think the part "DEFAULT" is the problem. But I did not find a configuration to get the same question like XP. The Server runs with Netware 5.

Greeting Peter
Labels (1)
0 Likes
10 Replies
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

Hello Peter,

Can you confirm that your NetWare 5 server is configured for TCP? It is possible that it was setup to only use the IPX protocol.

Are you able to connect to your Netware 5 server by specifying the server's IP address for the both the tree and the server?
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re:Win10 no tree

p borchert Wrote in message:

> some time ago I installed win10 on a computer with XP. I can boot both.
> Now I want to add a Novell client. I tried some clients, but all I
> tried, did not show a tree. The last client I tried is the client for
> Win7.
>
> So I looked what happens on the wire:
>
> *With XP there are two calls:*
> ' [img]http://privat.pb-edv-consulting.de/ipicture_library/XpBaum1.JPG]
> ' (http://privat.pb-edv-consulting.de)
> -------------------------------------------------------------------------------------------------------------------
> ' [img]http://privat.pb-edv-consulting.de/ipicture_library/XpBaum2.JPG]
> ' (http://privat.pb-edv-consulting.de)
> -------------------------------------------------------------------------------------------------------------------
>
> *With win10 there are 5 calls using different source-ports. One of
> them:*
> ' [img]http://privat.pb-edv-consulting.de/ipicture_library/10Baum.JPG] '
> (http://privat.pb-edv-consulting.de)
>
> With XP I get the tree and can login. With Win10 there is no tree
> displayed and no login. On the wire there is no answer fron the Server.
> I think the part "DEFAULT" is the problem. But I did not find a
> configuration to get the same question like XP. The Server runs with
> Netware 5.


As Kevin indicates, Windows 10 doesn't support IPX so you need to
have TCP/IP configured on your NetWare 5 server. You'll also want
the latest Novell Client for Windows 10 which is available for
download at https://download.novell.com/Download?buildid=eFifpCHJslA~

HTH.
--
Simon Flood
Micro Focus Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/
0 Likes
p_borchert Absent Member.
Absent Member.

Re: Win10 no tree

Hello Kevin,

thank you for your answer.

KBOYLE;2450792 wrote:
Hello Peter,

Can you confirm that your NetWare 5 server is configured for TCP? It is possible that it was setup to only use the IPX protocol.


The server is configured for TCP, may be for IPX too.



XP uses UDP and there is an answer. Win10 uses UDP and there is no answer.



There is a different question. May be "DEFAULT" is the reason that there is no answer.

Greetins Peter
0 Likes
p_borchert Absent Member.
Absent Member.

Re: Win10 no tree

Hello Simon;

thank you for your answer. I'll try this client too. When I tried the first time to use "Client for Open Enterprise Server" I did not find any call of the client on the wire. So I tried other clients.

Greetings Peter
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

p_borchert;2450800 wrote:
Hello Kevin,

The server is configured for TCP, may be for IPX too.

Greetins Peter


Hi Peter,

From the image you provided...



I see a UDP packet is sent to port 427. This port is used by the Service Location Protocol (SLP).

SLP is used to locate your NetWare/OES server(s). Beyond that, I don't know all the specifics.

I suspect the Novell/OES Client is looking for a server and not finding one. That is likely why you don't see the tree. One reason for this may be that the server is not configured for TCP.

Here are a couple of things I would like you to try:

  1. If your NetWare 5 server is configured for TCP, you should know the IP address. From the Client, enter the IP address into the Server and Tree fields when logging in. Are you able to login this way?
  2. If you can't find out what the IP address is, then perhaps the server doesn't have one because it is not configured for TCP. Reinstall the Client on your Windows XP machine and, during the initial configuration, be sure to specify both TCP and IPX protocols. If your XP machine now sees the server/tree, that would pretty much confirm your server is only using the IPX protocol.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

KBOYLE;2450813 wrote:
Hi Peter,

If you can't find out what the IP address is, then perhaps the server doesn't have one because it is not configured for TCP.


If your NetWare 5 server is not using TCP, you will not be able to access it from Windows 10 because Windows 10 does not support the IPX protocol.

If Windows 10 needs to access your server, you will have to modify your server to use TCP. You can just add the TCP protocol so that it uses both TCP and IPX.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
p_borchert Absent Member.
Absent Member.

Re: Win10 no tree

Hello Kevin,

thank you again. Well, UDP is part of TCP/IP and with WinXP the server answers.

I tried a ping to the server, it was ok. I tried a login with manual entered IP-address and context and had a login!

And now I remember: when XP was quite new, I tried a pur IP client, but the tree was not found. For a quick solution I installed IPX and the tree was found! The server runs with IPX and TCP/IP because there was a DOS-client runing as printserver.

I've got a work around.
Question: How can I see the tree without removing IPX at the server? Sometimes older machines with Win98 and special programms are used.

Gretings Peter
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

p_borchert;2450872 wrote:
Question: How can I see the tree without removing IPX at the server? Sometimes older machines with Win98 and special programms are used.

You should not need to remove IPX.

Now that you have verified that your NetWare 5 server uses TCP, you should be able to login from Windows XP and Windows 10 by entering the IP address of the NetWare server in the OES Client Tree and/or the Server fields. If that works for Windows 10 as well as Windows XP, then the only issue that remains is locating the server automatically.

The server is located via the Service Location Protocol (SLP). Make sure it is configured correctly and that your firewall(s) aren't blocking the required ports. Be sure to check the local firewall in your workstation OS(s).

Please let us know what you find.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

KBOYLE;2450876 wrote:
The server is located via the Service Location Protocol (SLP).


A few years ago Novell removed most of the online information for products they no longer support so you may have to use a search engine to locate the information you need.

Here are some TIDs dealing with SLP:


If you still require additional support, there is only one NetWare forum. You may ask here:
OES-NW: Install-Upgrade
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Win10 no tree

In article <p_borchert.7tv6rb@no-mx.forums.microfocus.com>, P borchert
wrote:
> thank you again. Well, UDP is part of TCP/IP and with WinXP the server
> answers.


So as part of that you should now know what the IP address of the server
is. Next step is to ping it, first from the XP instance to make sure you
can actually ping the server, then see if you can do the same from the
Win10 instance.
If Pinging works, put that IP in the Server field in the advanced
options as a work around to connect you.
Getting SLP sorted out is still your best bet to keep all running best
in the long run. The defaults between NetWare era and Linux based OES
changed just as the things did on the client for Windows Vista and up.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.