Error 6735 trying to configure Express on a Windows wireless network

Question

Level 1

0 points

Error 6735 trying to configure Express on a Windows wireless network

I have a small wireless network for three PCs implemented using a D-Link DI-624 router.
Just purchased an Airport Express.
Installed the software, including updates downloaded from Apple.
Connected Express via ethernet cable to the router.
Airport Utility for Windows 5.2.1 eventually recognises the Express, but when I click Continue to configure, it attempts to read the base station configuration, then displays error 6753, "An error occured while trying to access the base station. Make sure your network connection is valid and try again."
I have turned off encryption on the router, turned off the firewall software on the PC, and read nearly every forum posted on the subject on the WWW!

Does anyone have any ideas for me to try? Thanking you in advance for any assistance.

PC, Windows XP

Posted on Oct 11, 2007 5:56 AM

Reply

Answer 1

Tesserax

Level 10

148,453 points

Oct 11, 2007 7:44 AM in response to g_wnoble

Hello g.wnoble. Welcome to the Apple Discussions!

Although having the AirPort Express Base Station (AX) connected to your D-Link router should have made it accessible via the AirPort Utility, have you tried connecting it to your PC directly instead?

Reply

Answer 2

punidrop

Level 1

0 points

Oct 11, 2007 8:16 AM in response to Tesserax

Hi,

I just bought an Airport Extreme N. It works fine with my PowerBook but not my PC.
I connect my PC Desktop to Airport with LAN cable and have all the latest software.
When I run Airport Utility it recognize an Airport but unable to access it.
All I got is error number 6753.

Is anyone knows hoe to solve this?
Thanks in advance.

Reply

Answer 3

Tesserax

Level 10

148,453 points

Oct 11, 2007 8:33 AM in response to punidrop

Hello punidrop. Welcome to the Apple Discussions!

When your PC is connected to the AEBSn, do you have Internet connectivity? Is it just that you can't access it with the AirPort Utility?

Reply

Answer 4

punidrop

Level 1

0 points

Oct 11, 2007 8:55 AM in response to Tesserax

I have a DSL modem connected to Airport.(connect using PPPoe)
I can't access it with Airport Utility and lost Internet connectivity at the same time.
When I try to dial it says "The remote computer does not respond."

Message was edited by: punidrop

Reply

Answer 5

Tesserax

Level 10

148,453 points

Oct 11, 2007 9:22 AM in response to punidrop

From which device (Mac or PC or both) are you unable to:
1) Access the 802.11n AirPort Extreme Base Station (AEBSn) via the AirPort Utility?
2) Access the Internet?

Reply

Answer 6

g_wnoble Author

Level 1

0 points

Oct 11, 2007 1:43 PM in response to Tesserax

Hello Tesserax. Thanks for your quick reply.

I have connected it directly to the PC, via ethernet. The LED on the AX flashes amber (was green on the router), but the Airport Utility did find it (page listed a new IP address for it too) but clicking Continue results in the same.

Reply

Answer 7

Tesserax

Level 10

148,453 points

Oct 11, 2007 2:22 PM in response to g_wnoble

The LED on the AX flashes amber (was green on the router), but the Airport Utility did find it (page listed a new IP address for it too) but clicking Continue results in the same.

In this configuration, the flashing amber status light would be correct, as we removed it from the network. However, although "seeing" the AX in the utility is good, not being able to access it, of course, is not.

Please try a "factory default" reset, and then, try again to access it with the utility while still connected with the PC.

Reply

Answer 8

punidrop

Level 1

0 points

Oct 11, 2007 8:01 PM in response to Tesserax

My MAC works fine with both Airport Utility and Internet connection. (via wireless)
My PC Laptop can join wireless successfully. (it's sp1)
My PC Desktop can use Airport Utility to see AEBSn but CANNOT access neither Internet nor using Airport Utility.
I connect my Desktop using LAN cable.

wonder why is that...

Message was edited by: punidrop

Reply

Answer 9

Tesserax

Level 10

148,453 points

Oct 11, 2007 9:27 PM in response to punidrop

Ok, the issues that you are bringing up are deviating significantly from the original post and may require a completely different solution which will not benefit the Originator. I suggest that you create a new post in the AirPort Extreme (802.11n) Discussion area and provide the make/model of your PC desktop, and the make/model of the wireless card. Also include what you have tried already to resolve the issue. Thanks!

Reply

Answer 10

g_wnoble Author

Level 1

0 points

Oct 12, 2007 5:26 AM in response to Tesserax

+Please try a "factory default" reset, and then, try again to access it with the utility while still connected with the PC.+

Gave it a go. Did a factory default reset (4 green flashes of the LED) connected to the PC, and a minute or so, it did recognize the AX, But clicking Continue resulted in the same (error 6735).

Any other ideas?

Reply

Answer 11

Tesserax

Level 10

148,453 points

Oct 12, 2007 7:52 AM in response to g_wnoble

Just to make sure the installation of the AirPort Utility is not the cause, do you have another computer (Mac or PC) around that you can load the AirPort Utility on and try from it? ...or, if not, try uninstalling/re-installing the utility on your current PC.

Reply

Answer 12

g_wnoble Author

Level 1

0 points

Oct 12, 2007 3:44 PM in response to Tesserax

I have uninstalled/reinstalled the software numerous times now over this exercise.

As for the other computer, exactly what I thought overnight. I tried to install the software on my son's PC, but I think the processor is so old that the software wouldn't even run! Keep crashing, and wanting to send a report to Microsoft! sigh...

My next attempt will be to install on a friends PC and try that. Will let you know.

Reply

Answer 13

g_wnoble Author

Level 1

0 points

Oct 14, 2007 3:07 PM in response to Tesserax

OK. Went to my friend's place and hooked up the AX. At first, exactly the same thing happend. Error 6735. Then all of a sudden, it worked! Don't know why because I did do anything (except click "Continue" a second time).
Anyway, configured it up to my wireless network specs and took it home.
Plugged it in, and the AX went green, the Express Utility software recognised it, and iTunes showed it the list of speakers.
The problems are that I cannot select the speakers even though they are displayed AND I still can't configure the AX through the utility (Error 6735).
After a 10 minutes or so (I haven't timed it specifically), the base station drops off the Airport Utility software and iTunes. Doing a rescan in the Utility doesn't find the AX. The AX does stay green though.

Have I just got a dud AX? Should I go back for a replacement?

Reply

Answer 14

Tesserax

Level 10

148,453 points

Oct 14, 2007 3:16 PM in response to g_wnoble

Have I just got a dud AX? Should I go back for a replacement?

Hmm, sounds like it. It would probably be my next step to take it back for exchange ...

Reply

Answer 15

g_wnoble Author

Level 1

0 points

Oct 20, 2007 4:59 AM in response to Tesserax

OK, I've returned the AEX (twice, I'm on my third one now!) each time the same problem. I've been on the phone with Apple support for hours, and they don't know the answer. After more research on the Net, here's what I've done now.
1. Connected the AEX to the cable modem, making it the wirless router.
2. Installed a wireless card into my main PC (was previously connected directly to D-Link router)
3. Found the AEX wirelessly and configured it to work in client mode and join my existing wireless network. So far so good.
4. Installed iTunes. It listed the base station as a set of remote speakers, but try as I might I could not select them. Also, after 10 minutes or so, they disappear from iTunes. Also, the base station disappears from the Airport Utility. Switching the AEX off and on, brings it back. But for about 10 minutes or so.

As this is the third AEX, I don't think its the problem. I can configure the thing, but something is still wrong.

Ideas?

Reply