Connections to netware over IP 2

[DaveBrown]

Hi All,
Does anyone know if "Problems using underscore in the server name and IP connections. -TID10018822"
is still valid for Netware 5.1 as we have a netware 5.1 server where authentication is via IP but the normal connection is then made using IPX.
This one server has IP and SLP configured just the same as any of the other Netware 5.1.servers

PS
All netware servers are patched to SP7 and clients are running a mixture of Operating systems from win9x to win2k/xp

Thanks in advance

Dave

 

[terry712]

should connect ok - it is imho bad practice to use an underscore on any os

 

[DaveBrown]

Thanks Terry712 for the info - I've configured a test win9x workstation to connect to the particular server and its connects ok over IP. If I have any connectivity problems with this server in the future is it possible to set up and alias without an underscore rather than have to reconfigure all the live workstations which connect to this server?

Thanks again

Dave

 

[terry712]

not really - as you slp will not pickup the change and the clients will have the underscore - and your then not converting name to name - ie your resolving the wrong thing

sorry if my english sucks

my preference is that nop server is mentioned on the client
i always leave the server blank
and then distrib the slp info through dhcp

you could also distrib the preferred server over dhcp as well
this should over-ride it but not an option i use so you would need to test

 

[marvhuffaker]

I find it very odd that you are authenticating via IP but connecting via IPX.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[TheLad]

So do I. Maybe you could switch IPX off on the server, then maybe a DNS alias without the underscore in the servername might help? You would have to change your login scripts to reflect the change, I have seen this done in a test environment with some results, so test it first if you wanted to go down this route.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveBrown]

Thanks everyone - you have given me some "food for thought"
To Marvhuffaker - when I configure "Service Location" with server name and IP address then the workstation connects via IP - maybe I need to use ACU to push out these settings - its something I've looked at before but I've not been on a formal NW5 Admin / Advanced Admin course to see how to get the best out of it and now we have better / faster links between the remote sites.

Thanks again

Dave

 

[TheLad]

If you use NetWare for DHCP, you can also configure those settings and the workstation gets configured with them when they get a DHCP address

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveBrown]

Thanks "TheLad" - but there was a "political" decision not to use DHCP several years ago and we are stuck with static addressing for the forseeable future

Dave

 

[marvhuffaker]

just a note on the side.. You could come up with a compromise with your DHCP... Use DHCP but assign static addresses. At least that way you have control of who has what. And when you do need to implement a change company wide, you can do it from one point of reference instead of touching all PC's.

I gotta clear up the IP/IPX thing.. I'd like to understand your process.. Do you mean that at the login screen, for the server name, you enter the IP address -- but then in the connection tab after you've logged in, it shows you're connected via IPX? It's very possible that you think you're authenticating via IP but you're really not. Or IP is how you are originally connecting, but then your preferred protocol tells it to make an IPX connection? Just fishing here. The IP vs. IPX thing is fascinating because it's so complex and there are so many different ways that the process can be done.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support