B
Bing
I can see the novell server fine from win98/95 but not from
my win2000 professional. What can I do?
my win2000 professional. What can I do?
K
Keith V. Klenke
START with this checklist, make sure you do EVERYTHING on it, then report
back
what kind of packet sniffing/troubleshooting/etc have you done so far?
Ethereal and Novell's Packetscan are a couple freebies you'll want to take a
look at...
Guidelines to Take a Packet Trace
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10011012.htm
Packetscan - NetWare packet capture tool
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2967287.htm
How to use Ethereal to capture a packet trace.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10070788.htm
How to configure a capture filter for Ethereal
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10084702.htm
make sure you are using the latest nwclient & patches
http://support.novell.com/filefinder, http://download.novell.com
Make sure you have rolled it out via ACU & disabled NMAS if you do not need
it.
run through everything at http://www.ithowto.com/novell/clientspeed.htm
make sure DS is clean & healthy
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10060600.htm
make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct -
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085899.htm youll
want to make sure server & workstation are configured.
SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up) - service location protocol,
useful even in a small 5 person office all the way up to the largest
companies around. (how many users do you have anyways?)
http://www.srvloc.org/,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014570.htm,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10024591.htm. You
set this up, then push the options out via dhcp. If using DHCP to deliver
the information, please disable 'Active Discovery'
Internal DNS setup properly (yes, you do want to set this up) - you can use
sys
ublic\dnsdhcp console (run the setup from there) or iManager for dns (&
dhcp).
DHCP - you want this setup internally, because you can push out dhcp options
to clients that your WG router cannot, such as SLP, & static ip addressing
is pointless with reserved dhcp addresses.
latest drivers for everything (nic/chipset/controller/etc)
that speed/duplex on *everything* is hardset, & hardset correctly. Make sure
the switches have 'Spanning Tree' disabled or enabled 'Port
fast' on each workstation port. Any port with a single client attached to it
should be set with Portfast ON. It depends upon the switch manufacturer on
which option to select here & if connected directly to switch or via
unmanaged miniswitch...hopefully you arent stuck on hubs still.
check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)
purge all volumes & turn off compression - there are many utilities out
there that allow you to do automated purges, check out the links section
under www.abend.org
make sure there is more than 10% free space on EVERY NetWare volume
make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date
Microsoft Office slow - Other things that may make it
slow is office itself isnt up to date (you do have enterprise version & roll
it out/update via AIP right?), and drive mappings to slow remote servers or
servers that no longer exist. If you are using nwclient49sp1, make sure you
rolled it out via ACU with nmas disabled (www.appdeploy.com has ACU info).
Remember that winme & winxphome are not supported by ANYONE on a network,
including Microsoft. Novell's nwclients do work on these products, but your
mileage may vary, as they are not supported.
--
Thanks,
Keith V. Klenke
--------------------------------------------------
Hey everyone,
I just wanted to let you know there is a site that may be of some use. A
lot of people who work with Novell products, and are VERY good with
implementations and troubleshooting, frequent the site. You can find it at:
http://www.abend.org
back
what kind of packet sniffing/troubleshooting/etc have you done so far?
Ethereal and Novell's Packetscan are a couple freebies you'll want to take a
look at...
Guidelines to Take a Packet Trace
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10011012.htm
Packetscan - NetWare packet capture tool
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2967287.htm
How to use Ethereal to capture a packet trace.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10070788.htm
How to configure a capture filter for Ethereal
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10084702.htm
make sure you are using the latest nwclient & patches
http://support.novell.com/filefinder, http://download.novell.com
Make sure you have rolled it out via ACU & disabled NMAS if you do not need
it.
run through everything at http://www.ithowto.com/novell/clientspeed.htm
make sure DS is clean & healthy
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10060600.htm
make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct -
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085899.htm youll
want to make sure server & workstation are configured.
SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up) - service location protocol,
useful even in a small 5 person office all the way up to the largest
companies around. (how many users do you have anyways?)
http://www.srvloc.org/,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014570.htm,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10024591.htm. You
set this up, then push the options out via dhcp. If using DHCP to deliver
the information, please disable 'Active Discovery'
Internal DNS setup properly (yes, you do want to set this up) - you can use
sys
ublic\dnsdhcp console (run the setup from there) or iManager for dns (&dhcp).
DHCP - you want this setup internally, because you can push out dhcp options
to clients that your WG router cannot, such as SLP, & static ip addressing
is pointless with reserved dhcp addresses.
latest drivers for everything (nic/chipset/controller/etc)
that speed/duplex on *everything* is hardset, & hardset correctly. Make sure
the switches have 'Spanning Tree' disabled or enabled 'Port
fast' on each workstation port. Any port with a single client attached to it
should be set with Portfast ON. It depends upon the switch manufacturer on
which option to select here & if connected directly to switch or via
unmanaged miniswitch...hopefully you arent stuck on hubs still.
check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)
purge all volumes & turn off compression - there are many utilities out
there that allow you to do automated purges, check out the links section
under www.abend.org
make sure there is more than 10% free space on EVERY NetWare volume
make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date
Microsoft Office slow - Other things that may make it
slow is office itself isnt up to date (you do have enterprise version & roll
it out/update via AIP right?), and drive mappings to slow remote servers or
servers that no longer exist. If you are using nwclient49sp1, make sure you
rolled it out via ACU with nmas disabled (www.appdeploy.com has ACU info).
Remember that winme & winxphome are not supported by ANYONE on a network,
including Microsoft. Novell's nwclients do work on these products, but your
mileage may vary, as they are not supported.
--
Thanks,
Keith V. Klenke
--------------------------------------------------
Hey everyone,
I just wanted to let you know there is a site that may be of some use. A
lot of people who work with Novell products, and are VERY good with
implementations and troubleshooting, frequent the site. You can find it at:
http://www.abend.org