Bug 188085 - Cannot connect with a backslash in the username
Summary: Cannot connect with a backslash in the username
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: KDED Module (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 16:48 UTC by Pierre-Luc Auclair
Modified: 2011-05-09 06:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Luc Auclair 2009-03-25 16:48:32 UTC
Version:            (using KDE 4.2.1)
Installed from:    SuSE RPMs

When connecting to a MS network which requires a "domain", you need to type in a backslash in the name in this manner:
domain\username

Doing so with knetworkmanager seems to be working fine, but with the KDE4 network manager there seems to be some trouble. When configured properly, it will not connect but stay with at "plug" icon instead of switching to the round "I'm working" animated icon although the gui says "Connecting Hotspot". It seems to be failing directly after that.

This is the configuration file, as you can see there's an escape backslash before the backslash:
[802-11-wireless]
band=bg
bssid=
channel=0
macaddress=
mode=infrastructure
mtu=0
rate=0
security=802-11-wireless-security
seenbssids=
ssid=UQAM Wi-Fi
txpower=0

[802-11-wireless-security]
authalg=open
group=
keymgmt=WPAEAP
leapusername=
pairwise=
proto=
securityType=WPAEAP
weptxkeyindex=0

[802-1x]
anonymousidentity=
cacert=
capath=
clientcert=
eap=peap
identity=ens\\hc291207
phase1fastprovisioning=
phase1peaplabel=
phase1peapver=one
phase2auth=
phase2autheap=mschapv2
phase2cacert=
phase2capath=
phase2clientcert=
phase2privatekey=
pin=
privatekey=
psk=

[connection]
autoconnect=true
id=UQAM Wi-Fi
timestamp=-4713,1,1,0,0,0
type=802-11-wireless
uuid={ebde2ac9-7b10-43f7-a580-86b32c354fa5}

[ipv4]
addresses=
dnssearch=\\0
ignoredhcpdns=false
method=Automatic
routes=
Comment 1 Will Stephenson 2009-08-16 23:00:36 UTC
Can you test this again with latest knetworkmanager?