problems with 10/100 hubs

[rich]

I work for a company that provides harrdware/software for Travel agents
Some agents have a backoffice sys running on netware 312
2 or 3 of these agents have upgraded there network to kat5 and 10/100
hubs also installed
Workstations on 10meg cards and so is the netware server
The problem is when you reboot the workstation it cant find the
server,if you then change the primary network logon from client for
netware networks to client for microsoft networks and reboot you get
connected
Reboot again and the same situation change from client for msn network
to netware and your back up again
Put 10meg hubs back in no more problems so I am thinking it is a
problem that netware has with auto 10/100 hubs?????????????

Any help would great

Rich

* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

[Dave Lunn]

Rich,

Setup you client for just 802.2 (assuming that's what the net is using)
rether than auto select protocol and you'll likely be happy.

Dave
rich <richardoho...@esatclear.ie.invalid> wrote in message
news:171233da...@usw-ex0107-049.remarq.com...

[rich]

Dave
the server is setup with 802.3 should I try changing it to 802.2 or
should I be locking at the workstations

Rich

In article <8vpgrr$jr...@nexus.provo.novell.com>, "Dave Lunn"

[Shaun Pond]

Rich,
802.3 will work, but 802.2 is better, as it supports checksumming. If
you can do it, I'd change the server to use 802.2 and force the
workstations to do so also. Note that if you have any print servers on
the lan, such as HP jetdirects, they will probably complain after the
change, just turn them off/on so that they relearn.

Shaun Pond
Novell Support Connection SysOp

[rich]

Thanks Shaun will give this a try this week and see what happens

[Dave Lunn]

Rich,

You need to go into the w95 properties to do that "force" when setting the
W/S to run one protocol. Also, I should have made the point Shaun raised
about the print servers. Your net might be old enough that you could have
print servers that *only* run 802.3, in which case you need to retain that
protocol and keep it bound to the server NIC even if you load and bind
802.2.

To do the load and bind for two protocols to one NIC don't forget you have
to have a name for the NIC.

Dave
rich <richardoho...@esatclear.ie.invalid> wrote in message

news:22ada760...@usw-ex0107-049.remarq.com...