treborsitnay
IS-IT--Management
Since I bought my Toshiba m205-s810 Tablet PC in July, I have not been able to resolve the following problem. (Note: I have Windows XP Tablet PC Edition v.5.0 (SP2) + all updates.)
I manage a small Windows 2000 Server network LAN/WAN that uses Active Directory for resource authentication and management. We have approximately 11 laptops and 16 desktops on the network. The network is split between two locations and joined via an IPSec VPN between Bell South T1 pops at each location.
All users at both sites logon to the MS domain via the PDS (primary domain server) at the manufacturing plant facility. The majority of PCs are connected via CAT5 Ethernet to either HP layer 2 switches or Linksys smart switches, and then to the Internet through a firewall/gateway and Bell South Cisco routers at each site. Several of the laptops are connected wirelessly to Linksys WRT54g 802.11b/g Router/firewall/APs, which are directly connected to the wired LAN via one of the 4 LAN ports.
All of the laptops can logon either via wired or, if their WiFi NICs support WPA authentication, wireless connections, and MAP network drives to the W2K Primary Domain Controller/DNS/WINS Server. That is, except for my Toshiba m205 tablet PC (the only tablet PC on our network). If I first connect the m205 via CAT5, or, have the WiFi NIC (internal) switched on, the m205 will not authenticate to the W2K domain – and the event log contains the following:
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 11/23/2004
Time: 11:19:56 AM
User: N/A
Computer: YANTISR-TAB-PC
Description:
The Security System could not establish a secured connection with the server cifs/basofil.local. No authentication protocol was available.
However, if I login via the XP cached credentials with the m205 disconnected wired & wirelessly, allow the OS load to complete, then connect the CAT5 cable or turn on the WiFi NIC, the m205 enables the static IP address assigned locally (we do not yet use DHCP for the wired connections due to some application-specific issues) or receives a dynamic IP from the WiFi router, and I can manually run the Active Directory login script (locally) to successfully MAP the appropriate network drives. And then all is well and functions normally as with the rest of the laptops (and desktops).
I have searched the web and specific forums extensively, both this one and other technical/expert ones, but cannot find an explicit reference or answer to this specific problem.
NOTE: Per the eventid.net forum:
I ran the 'netdom reset <machine> [domain:<local domain>] [server:<ads server>' commands as illustrated in the eventid.net/Microsoft docs, but did not help.
To recap: The weird aspect of this thing is that, so long as the M205 is not connected to the CAT5 LAN and the WiFi NIC is switched off when I login (to completion) to Windows (using the cached credentials of the local domain), then connect to the CAT5 or WiFi LAN, I can then successfully 'ping' the domain server (indicating successful authentication), MAP a network drive, or run my MAPing script locally without the errors. However if I connect the M205 to either the CAT5 or WiFi LAN before I attempt to login to Windows via the 'connected' local domain credentials, I get the errors. And even if I then disconnect the physical connection, I continue to receive the errors. Only by rebooting the disconnected M205 can I again go through the first procedure successfully and MAP drives and 'ping' the domain server.
Could this maybe be a problem specific to either the Toshiba m205 with the Intel Centrino chipset (NICs etc.), the Windows XP Tablet PC OS, driver versions, or combination(s) of these? I know ‘anything is possible’, but, I am hoping that someone has experienced this same problem and has found an answer that I can use to resolve this.
Thanks for any help or suggestions.
I manage a small Windows 2000 Server network LAN/WAN that uses Active Directory for resource authentication and management. We have approximately 11 laptops and 16 desktops on the network. The network is split between two locations and joined via an IPSec VPN between Bell South T1 pops at each location.
All users at both sites logon to the MS domain via the PDS (primary domain server) at the manufacturing plant facility. The majority of PCs are connected via CAT5 Ethernet to either HP layer 2 switches or Linksys smart switches, and then to the Internet through a firewall/gateway and Bell South Cisco routers at each site. Several of the laptops are connected wirelessly to Linksys WRT54g 802.11b/g Router/firewall/APs, which are directly connected to the wired LAN via one of the 4 LAN ports.
All of the laptops can logon either via wired or, if their WiFi NICs support WPA authentication, wireless connections, and MAP network drives to the W2K Primary Domain Controller/DNS/WINS Server. That is, except for my Toshiba m205 tablet PC (the only tablet PC on our network). If I first connect the m205 via CAT5, or, have the WiFi NIC (internal) switched on, the m205 will not authenticate to the W2K domain – and the event log contains the following:
Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 11/23/2004
Time: 11:19:56 AM
User: N/A
Computer: YANTISR-TAB-PC
Description:
The Security System could not establish a secured connection with the server cifs/basofil.local. No authentication protocol was available.
However, if I login via the XP cached credentials with the m205 disconnected wired & wirelessly, allow the OS load to complete, then connect the CAT5 cable or turn on the WiFi NIC, the m205 enables the static IP address assigned locally (we do not yet use DHCP for the wired connections due to some application-specific issues) or receives a dynamic IP from the WiFi router, and I can manually run the Active Directory login script (locally) to successfully MAP the appropriate network drives. And then all is well and functions normally as with the rest of the laptops (and desktops).
I have searched the web and specific forums extensively, both this one and other technical/expert ones, but cannot find an explicit reference or answer to this specific problem.
NOTE: Per the eventid.net forum:
I ran the 'netdom reset <machine> [domain:<local domain>] [server:<ads server>' commands as illustrated in the eventid.net/Microsoft docs, but did not help.
To recap: The weird aspect of this thing is that, so long as the M205 is not connected to the CAT5 LAN and the WiFi NIC is switched off when I login (to completion) to Windows (using the cached credentials of the local domain), then connect to the CAT5 or WiFi LAN, I can then successfully 'ping' the domain server (indicating successful authentication), MAP a network drive, or run my MAPing script locally without the errors. However if I connect the M205 to either the CAT5 or WiFi LAN before I attempt to login to Windows via the 'connected' local domain credentials, I get the errors. And even if I then disconnect the physical connection, I continue to receive the errors. Only by rebooting the disconnected M205 can I again go through the first procedure successfully and MAP drives and 'ping' the domain server.
Could this maybe be a problem specific to either the Toshiba m205 with the Intel Centrino chipset (NICs etc.), the Windows XP Tablet PC OS, driver versions, or combination(s) of these? I know ‘anything is possible’, but, I am hoping that someone has experienced this same problem and has found an answer that I can use to resolve this.
Thanks for any help or suggestions.