Opened 8 months ago

Closed 8 months ago

#1231 closed request (wontfix)

Windows 10 problem

Reported by: john-ietf@… Owned by: panda@…
Priority: tbd Milestone: ietf-102
Component: helpdesk Keywords:
Cc: My Current Location:
My MAC Address: 54:A0:50:39:45:82 My OS: Windows 10

Description

I am unable to connect to ietf or other secure SSIDs.

Change history (10)

comment:1 Changed 8 months ago by llynch@…

Component: incominghelpdesk
Owner: changed from Clemens Schrimpe to Rick Alfvin

Hi John -

Please swing by the terminal room and someone will take a look at your setup

  • Lucy

comment:2 in reply to:  2 ; Changed 8 months ago by Rick Alfvin

Hi Lucy,
John stopped by the help desk. We tried all the usual fixes. Nick suggested Clemens might be able to help with this.
Thanks,
-Rick


> On Jul 16, 2018, at 12:59 PM, IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
> 
> #1231: Windows 10 problem
> ------------------------------------+-----------------------------------
>      Reporter:  john-ietf@…        |                Owner:  Rick Alfvin
>          Type:  request            |               Status:  assigned
>      Priority:  tbd                |            Milestone:  ietf-102
>     Component:  helpdesk           |           Resolution:
>      Keywords:                     |  My Current Location:
> My MAC  Address:                    |                My OS:  Windows 10
>  54:A0:50:39:45:82                 |
> ------------------------------------+-----------------------------------
> Changes (by llynch@…):
> 
> * owner:  Clemens Schrimpe => Rick Alfvin
> * component:  incoming => helpdesk
> 
> 
> Comment:
> 
> Hi John -
> 
> Please swing by the terminal room and someone will take a look at your
> setup
> 
> - Lucy
> 
> -- 
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1231#comment:1>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:3 Changed 8 months ago by Rick Alfvin

Owner: changed from Rick Alfvin to Clemens Schrimpe

comment:4 Changed 8 months ago by Clemens Schrimpe

Sorry, but I honestly do not posses any knowledge about Windows 10. 😳

comment:5 Changed 8 months ago by llynch@…

so - Clemens can't really help - did you try the legacy ssid?
There is some windows related info in the old helpdesk wiki pages.

Who should I hand this off too?

  • Lucy

comment:6 Changed 8 months ago by llynch@…

comment:7 in reply to:  7 ; Changed 8 months ago by Rick Alfvin

We went down that road, sadly to no avail.

> On Jul 16, 2018, at 1:19 PM, IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
> 
> #1231: Windows 10 problem
> -------------------------------------+-------------------------------------
>      Reporter:  john-ietf@…         |                Owner:  Clemens
>                                     |  Schrimpe
>          Type:  request             |               Status:  assigned
>      Priority:  tbd                 |            Milestone:  ietf-102
>     Component:  helpdesk            |           Resolution:
>      Keywords:                      |  My Current Location:
> My MAC  Address:  54:A0:50:39:45:82  |                My OS:  Windows 10
> -------------------------------------+-------------------------------------
> 
> Comment (by llynch@…):
> 
> old info:
> 
> https://tickets.meeting.ietf.org/attachment/wiki/WindowsInformation/IETF
> Wifi Instructions Windows.pdf
> 
> -- 
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1231#comment:6>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:8 Changed 8 months ago by jim@…

Maybe he could sit with Panda and try? Panda may be able to determine exactly what's (not) happening...

comment:9 Changed 8 months ago by jim@…

Owner: changed from Clemens Schrimpe to panda@…

John will come to the NOC to talk to Panda around 2pm

comment:10 Changed 8 months ago by panda@…

Resolution: wontfix
Status: assignedclosed

Hi,

I took a look at this issue, and found it was not solvable because it was presumedly a client-side driver issue. No error logs were recorded on the controller and ARP and ND worked fine even when ping lost bits. I asked Joe to take a look at Cisco's database if this is a known issue. However, I think we cannot fix this issue during this meeting, so let me close the ticket.

Thank you.
Hirochika Asai

Note: See TracTickets for help on using tickets.