What am I doing wrong for the wireless connection in the Wing?
 

Everytime I go to the Wing, I cannot seem to connect. I've used two different laptops now. I see the Cathay SSID and choose that to connec to. But I don't get an IP address.

When I go to the Pier (on the same day), it works just fine.

Last visit to both lounges was 2 days ago.

Any suggestions?

When you get it figured out, please post here. Last time I was there, I messed around with my computer for two hours trying to get a connection... no luck.

My experience is also odd. The first time I used it at the Wing, it just didn't work, and I spent an hour or so fiddling around. It was also the first time I had used the wireless, since it was a new computer. Then, I went to ICN, and it worked just fine, no hassles from the get-go. Next time, it was at the Pier, and it worked fine also. My next time in the Wing, it also worked, no mucking around! Go figure.

Don't know, but it must be something that Microsoft worked on. You all know the joke if Microsoft made cars, they would stall for no reason, but you could get them to restart by walking out and opening and closing the trunk and the left rear door (in that order), and then pressing the wiper lever twice.

The DHCP Server is not 'leasing' IP addresses. If CX wants to fly me to HKG First, I will fix for free!

Christian

My experience is same. Successful Wi-Fi level connection with no-WEP key, but no IP address is leased from DHCP server.

CX's 'Wireless Internet set up procedure', which is available from a lounge attendant,
seems to say there are only 30 IP addresses for lease. One possibility is out of stock for IP address pool for leasing.

Pier has difference configuration of address pool.

Glad to see that it isn't me specifically. I'm going there again tomorrow and I'll let someone know about the problem.

Did any of you try the following:

- Click, Start, Run (assuming WinXP or Win2K)
- Enter CMD <OK>
- Enter at the command prompt:
ipconfig /release <enter>
- Enter again at the prompt:
ipconifg /renew <enter>

If in fact they have a hard limit of 30 users, doing this every once in a while forces a new IP renewal. Normally Windows XP or Win2K will give up after a first failure if in fact already 30 IP address leases were given.

I will try this experiment on Tuesday and report back.

So that's how one gets the DOS mode! In earlier versions of Windows you could type the command directly into the Run window.

The things one learns in FT...

Hi,

Yes, I did do the ipconfig release and renew. Didn't work either.

I was in the lounge first thing in the morning and didn't see anyone else there. Unless the router is not releasing any IP addresses from the previous night or there are many people stealing the IPs outside of the lounge, I'm not sure what's wrong.

Spoke to the agent at the front desk of the F class wing. They said they are aware of the problem and will be getting someone to look into it. I'm going to fill out a comment card as well. Good thing my flights have been out of the 60+ gates these past couple of weeks.

Do any Wing regulars remember what subnet the wireless used, the DNS IP and gateway/router IP?

You could always try a static entry if the router ISN'T releasing the IP, not nice if I ran the network but something IS hosed on their network....

I tried a few of the static IP that is on the piece of paper they give you. Still didn't work.

Even with instructions, help of the representatives (who really don't know that much at all about the WiFi in the lounges) I have had no success in getting it to work.

I've given up already. Now I don't bother with WiFi and head straight to the work stations instead. http://www.flyertalk.com/forum/smile.gif

Me too. Athough I was going to attempt screwing around with this some more, I decided my time would be better spent picking up some last minute gifts. Used the lounge-provided computers, instead.

Any idea when this supposed to happen? It seems like this problem has been ongoing for several weeks now and it seems very un-CX like for them not to have addressed this more promptly.