I am in the process of setting up my second TC10

[markpayton]

I am in the process of setting up my second TC100 and have noticed a behavior that troubled me with the first one, too. We have a Windows 2000 Active Directory based network, with all machines and users authenticating against the domain controllers. When I connect the TC1000 via wireless, login is incredibly slow (measured in tens of minutes), although it is as fast as any other machine when connected via the wire. My first unit seems to have overcome this obstacle after a time and now logs in as fast as any other wireless machine. I don't recall doing anything to correct this; it seems to have fixed itself after a few days.

Has anyone else experienced this or does anyone have any suggestions?

Thanks,
Mark Payton
Vermont Academy

[splintercell]

I have a 2-DC Active Directory setup at work, and login over the wireless on a TC1000 is just as fast as our other laptops over wireless - indiscernable from over the wire. Do you have a lot of policies and/or assigned software installations happening? Startup/logon scripts?

[markpayton]

We do have a fair bit of security, and a login script that does drive mapping. I noticed that the drive mappings were not happening, so there may well be something else at work here. Still, the other machine logs in fairly quickly--though not as fast as over the wire.

[MooseMaster]

Try setting a static IP address. I've had HUGE delays logging into networks because it has to find and assign IP addresses. When I set my own IP address it usually logs on with no delay at all.

[Dennis Rice]

Slow bootup and login is usually due to DNS issues....!

[markpayton]

We do use DHCP, and there is a second level of DHCP with the current wireless APs we are testing, but that wouldn't explain why it is slow for a while, then speeds up. I haven't had any slow logins on the first unit in weeks.

[MooseMaster]

I'd bet that WindowsXP records a range of IPs that it has been assigned in the past and only searches in that range, and thus speeds up the processes. I don't know if Microsoft made WinXP that smart, though. :/

[GF]

quote:Originally posted by markpayton

We do use DHCP, and there is a second level of DHCP with the current wireless APs we are testing, but that wouldn't explain why it is slow for a while, then speeds up. I haven't had any slow logins on the first unit in weeks.


It depends on the DHCP setup. If the ip address is set to expire after 8 hours, when you connect to the network after expiry it needs to locate the DHCP to obtain a new ip address. Otherwise, it will use the existing IP address. I think this is the only way to explain your current situation.

[detayls]

I've had exactly this problem.

Turn on the DNS server on your domain controller. Then the fix is to add your domain controller's IP address to the DNS list on your Tablet or add the domain controller's name and IP to the hosts file at C:\WINDOWS\system32\drivers\etc.

Mine looks like this, where my domain controller's name is sleepinglady:

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
192.168.17.99 sleepinglady

[Caffiend]

Ok, I've had some issues with AD and the TC1000 connecting or even functioning properly in the network. I create an AD account for the tablet in an unrestricted OU. Once it is determined what restrictions the tablet will need, I'll move it into the corresponding restricted OU. Anytime I move the account, or rename the tablet, I can no longer manage it. The tablet will connect to the network and appears to function normally. Also, AD doesn't appear to update when I change the name on the tablet. (either that, or it is taking days to update. Any ideas? All our tablets use Cisco wirless 350.