The same setup on T42 or HP laptops and I have no problems. Any ideas?
> I have no problems if the wireless card is disabled.
It could be hardware problem, have you contacted IBM ?
Have you tried updating the wireless NIC driver ?
Any information on the event log ?
--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
There is a known issue with Novell clients 4.91,sp1,sp2. and the native
wireless services. Novell TID10099783
To fix your issue modify the windows service: "Wireless Zero
Configuration" startup type setting to AUTOMATIC.
Hope this helps.
After pressing CTRL+ALT+DEL there is a 2 minute delay before the NWGINA
appears.
http://support.novell.com/cgi-bin/search/searchtid.cgi?10099173.htm
Using Bootvis some of us have isolated svchost.exe (mrxsmb.sys) getting hung
during startup when 1 - 2 minute delays were present.
Lets gather some more details about your environment...
Any additional components of the client installed?
What protocols are bound to the client?
Windows Event logs showing anything unusual?
Was Windows installed from scratch, a custom image, or an OEM image?
Security or any other driver-based software like firewall, VPN, remote
management or antivirus installed and running?
BootVis is be a good troubleshooting option for general startup delays.
1.3.37.0 can be downloaded from various web sites to help you troubleshoot
where delays are present in XP's startup...
Fast Boot / Fast Resume Design
http://www.microsoft.com/whdc/system/sysperf/fastboot/default.mspx
http://www.tweakhound.com/xp/bootvis/
Can you verify a virus, spyware or some other corruption has not affected
Windows?
I've used these utilities in the past to help troubleshoot and they can tell
you wonders about what is really going on with Windows...
AutoRuns, Process Explorer, Filemon, Regmon, LoadOrder, TCPView, and TDImon
http://www.sysinternals.com/
DriverView and ServiWin
http://www.nirsoft.net/utils/
--
Tony Pedretti
TransUnion Corporation
Our symptom was like what the original post stated, and we saw the delay
from the time the power was turned on to when the Novell Client Login came
up.
When we applied the fix which was published by Microsoft as this TID
states, our issue cleared up immediately.
Novell's recommended fix for 4.91sp2 was to apply 491PSP2_CONN.EXE and
remove the following key from the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Dep
endOnService
We chose to go the other route just because we could to that much quicker.
Pete Karasz
I was involved with this issue originally so I'm curious if there have
been new developments.
Do you have any more details? Updated with the other symptoms?
Sounds like Novell support is recommending clearing the DependOnService
registry value and applying the Connectivity patch as an initial
troubleshooting step for slow startups/login.
I received the same advise during an iPrint service request I had opened
with them involving delayed system startup and login.
I agree with applying the patch but you would need to prove to me the
delay is in the Novell Service Location(SRVLOC) service itself and not
in the config of SLP or third-party interference...
"Tree or server not found" error on bootup and immediate login
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086186.htm
Server or Tree not found after applying Windows XP sp2
http://support.novell.com/cgi-bin/search/searchtid.cgi?10095407.htm
NetWare Client registry settings to control the behavior of SLP
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086052.htm
--
Tony Pedretti
Not more than I mentioned in my previous post. I was actually
troubleshooting an isse with installing Imanager with an eDirectory Expert,
and while we were waiting for something I just started to mention this to
him and asked if he was familiar with it. He wasn't but he said he had
access to the person responsible for the "Novell Client" so he took the
information to him and the recommendation I posted was from that person
directly. I imagine something is forthcoming.
We stripped the notebooks down as much as possible and then modified the
Wireless setting and they broke every time. I imagine this is also visible
in many other models of notebooks. The ones we had the issue in were
HP6220/IntelWireless, Dell models with integrated and with Cisco 350
wireless cards.
Pete
also found that this was mainly an issue in our office, where there is
no wireless access point (yet). when I brought a laptop home and tried
it on my home wireless, it booted right up, with hardly any delay.
there is about a 10 second delay with windows managing the connection,
but thats way better than 1-2 minutes. seems to me that its searching
for a connection, and won't give up till it finds one, or the user
falls asleep. even windows can find one at my house in a reasonable
amount of time.
--
chuck