Wireless Problem

[wesleyw]

Okay so I've setup up WAPs using the WEP encryption (I know its insecure but I've been having trouble with laptops detecting it and using it properly).

I have Intel PRO/Wireless 2915ABG on a laptop I setup the WEP and my own laptop has the intel 39?? chipset this finds and connects prefectly however the 2915 doesn't can't find it! This morning I come in without changing a thing and the bl**dy 2915 logs on using it! I prohibit the SSID broadcast and now it can't find anything again even when I change it back!

HELP!


Wes

[plexer]

Don't set your WAPS not to broadcast their SSID this does naff all to increase the security and can cause problems as you've seen.

Ben

[djm968]

Yes agree, switching the SSID broadcast beacon off is as good a security measure as Win9x asking you for a password!

[Geoff]

Um, if you've installed the WPA2 patch for WinXP it'll display AP's with 'hidden' SSIDs.

Hidden SSIDs, MAC filtering and WEP are not secure. Don't bother wasting your time with them. Just use WPA/WPA2.

[bishopsgarthstockton]

sometimes i find if you give the laptop or PC a reboot, clear the cache that helps pick up the wireless devices.

but def do not dissable ssid

[wesleyw]

@Geoff: Windows 2003 seems to only support WPA as well can that patch be safely installed on the server too?


Wes

[wesleyw]

I've found when I leave the laptop opver night it can find the AP again however it still can't connect because of some problem with the WPA setup.

Wes

[Geoff]

@Geoff: Windows 2003 seems to only support WPA as well can that patch be safely installed on the server too?

As I understand it, the WPA2 patch was included in SP1 for W2k3.

[plexer]

You can't create wireless policies using wpa2 in server 2003 sp1.

The Wireless Network (IEEE 802.11) Policies Group Policy extension for Windows Server 2003 with SP1 does not support the configuration of WPA2 authentication settings. To configure WPA2 authentication settings in the Wireless Network (IEEE 802.11) Policies Group Policy, you must install the Wireless Client Update for Windows XP with Service Pack 2 on wireless client computers that are running Windows XP with SP2. Then, you must configure WPA2 settings in Group Policy from a computer that is running Windows Vista or Windows Server "Longhorn."

From:
http://www.microsoft.com/technet/com...uy/cg0505.mspx

[wesleyw]

What a pain

Okay I'll set it up as WPA and then have a go!


Wes

[wesleyw]

OKay then I've setup the WPA system, it brought up an error about cannot find cert but I've sorted that I think. Now it's just messing me about with the certificate. lol

Wes

[wesleyw]

System Events

EVENT ID 4
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server IT03-03$. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (QMGS.INTERNAL), and the client realm. Please contact your system administrator.


EVENT ID 1007
Your computer has automatically configured the IP address for the Network Card with network address 00166F569CFA. The IP address being used is 169.254.147.69.


BTW it03-03$ is a client not a server any ideas?

[Geoff]

Run netdiag on IT03-03.

[wesleyw]

I've also got this in the server's system event log with regards to the WPA connection:

User host/MCLdefault.QMGS.internal was denied access.
Fully-Qualified-User-Name = QMGS.internal/Learning Network Manager/Labs/School Mobile Lab/MCLDEFAULT
NAS-IP-Address = 192.168.1.118
NAS-Identifier = <not present>
Called-Station-Identifier = 00-0C-46-F6-91-58:QMGS
Calling-Station-Identifier = 00-16-6F-56-9C-FA
Client-Friendly-Name = WAPQMGS2
Client-IP-Address = 192.168.1.118
NAS-Port-Type = Wireless - IEEE 802.11
NAS-Port = 1
Proxy-Policy-Name = Use Windows authentication for all users
Authentication-Provider = Windows
Authentication-Server = <undetermined>
Policy-Name = Connections to other access servers
Authentication-Type = EAP
EAP-Type = <undetermined>
Reason-Code = 65
Reason = The connection attempt failed because remote access permission for the user account was denied. To allow remote access, enable remote access permission for the user account, or, if the user account specifies that access is controlled through the matching remote access policy, enable remote access permission for that remote access policy.

Any thoughts on this?


Wes

[wesleyw]

@Geoff: When I run netdiag on my machine I get the following error message even though it works fine on the server: