New gadget

[Gary]

Thanks Gary, it does explain some things, but it also says I need to disable DHCP on the router to enable a static IP, and I'm concerned about messing up the current settings for the laptop.  I think what I might do is take this Eee PC out and see if it will connect to an unsecured wireless hotspot, and take things from there.  Even if I get it to work here, with a static IP, that's not going to be much use if I'm not within range of my own router, is it?

I see your point, if you cant link to a hotspot its not much good, you can't ask Starbucks to disable their DHCP really

[Rik]

I wonder if it's possible to come at it from the other end by getting the router to give the Asus a static address?

[Gary]

I wonder if it's possible to come at it from the other end by getting the router to give the Asus a static address?

The router should be able to assign a static IP, Rik. I remember the 2700 had that option for devices you connected wifi on the BT firmware, but its a long time since I used one

[Rik]

I do it with my laser printer, Gary, so I know the technique works in Windows.

[Steve]

Sorry if I confused as I understand it the DHCP server on the router has a list/range of addresses that it will automatically allocate a connected device to i.e 192.168.1.33-192.168.1.66 So if you wish a device to have a static ip address you have to give it an address outside this range i.e 192.168.1.30. the rest of the devices can still be connected automatically via DHCP. One comment suggested looking at the router web page from another computer to see how the EEc Pc was connecting.

[Gary]

I do it with my laser printer, Gary, so I know the technique works in Windows.

I agree Rik, but this is Linux though but it should i would have hoped be similar, Ted is one of the Linux masters so he would know possibly, but I confess it seems a lot of hassle and god knows what happens when you take the thing out to a wifi hotspot

[Gary]

Sorry if I confused as I understand it the DHCP server on the router has a list/range of addresses that it will automatically allocate a connected device to i.e 192.168.1.33-192.168.1.66 So if you wish a device to have a static ip address you have to give it an address outside this range i.e 192.168.1.30. the rest of the devices can still be connected automatically via DHCP. One comment suggested looking at the router web page from another computer to see how the EEc Pc was connecting.

That makes sense, Simon could log it his router and see what's happening when the EEc Pc connects, but what about connecting to other wifi networks?

[Simon]

There is no sign on the router of any existence of the Eee PC.  I have even just tried connecting via Ethernet, and it won't have it, saying  "Connect (38,0): No such device."  I assume this is referring to the VCI / VPI setting, which is correct.  I'm about to email Expansys to return the unit, as I can't be bothered with all this.   

[Gary]

There is no sign on the router of any existence of the Eee PC.  I have even just tried connecting via Ethernet, and it won't have it, saying  "Connect (38,0): No such device."  I assume this is referring to the VCI / VPI setting, which is correct.  I'm about to email Expansys to return the unit, as I can't be bothered with all this.  

Watch out as they charge a restocking fee for "Opened software" Simon, even if its faulty I had a run in with them about that, but if its that much of a pain I would say enough is enough and get a Arcam toy

[Simon]

I haven't opened the software, assuming it's the CDs they refer to, Gary.  I have just completed an RMA request, and am about to email it to them.  Shame, because it would have been a handy little gadget.

[Rik]

There is no sign on the router of any existence of the Eee PC.  I have even just tried connecting via Ethernet, and it won't have it, saying  "Connect (38,0): No such device."  I assume this is referring to the VCI / VPI setting, which is correct.  I'm about to email Expansys to return the unit, as I can't be bothered with all this.   

Shouldn't be VCI/VPI, Simon, as that's on the 'phone side' of the router. I wonder if it needs a driver loaded for the ethernet connection, or whether we're back to a DHCP issue?

[Inactive]

.  I'm about to email Expansys to return the unit, as I can't be bothered with all this.   

I can't say that I blame you Simon, I couldn't be bothered with all of that faffing around either.

It should have had a " Geeks Only " warning on the web page.

[Rik]

That wouldn't be  bad idea, In. People certainly need to understand that it's not like buying a Windows or Mac machine, and I suspect a lot do not.

[Gary]

I haven't opened the software, assuming it's the CDs they refer to, Gary.  I have just completed an RMA request, and am about to email it to them.  Shame, because it would have been a handy little gadget.

It is Simon so you will be fine

[Gary]

That wouldn't be  bad idea, In. People certainly need to understand that it's not like buying a Windows or Mac machine, and I suspect a lot do not.

When you spend that much time trying to get things to work you really do realise that Linux is more for and no offence meant here the dedicated hobbyist who has more time and patience than I would to get this up and running, it would drive me mad I think

[Steve]

How rarely these days do we use msdos commands within windows? Myself very rarely I have forgotten most of them. It appears to me (perhaps totally wrong )that unless you are familiar with the Linux command line structure you are going to struggle to get this device or similar to function if it fails to perform as intended.

[Rik]

I agree, Steve. I think you've got to be prepared to read up on Linux.

[Inactive]

But surely a computer of this type should at least be able to connect to the net, without too much difficulty, or am I missing something?

[Gary]

I agree, Steve. I think you've got to be prepared to read up on Linux.

Once you grasp the command lines im sure it falls into place but Apple and Windows in thier present incarnations have spoiled us with ease of use, which also gives us all the issues of security as well, Linux is much safer in many ways, but not ideal for every day use unless you have spent the time learning it, then I assume its relatively easy

[Simon]

But surely a computer of this type should at least be able to connect to the net, without too much difficulty, or am I missing something?

That's the point, In.  I have to say, much of the dialogue is very 'Windows like', and had it connected, I could have happily used the basic web and email functions without any trouble.  It's when you think you want to install a program, and quickly gather it's just not that simple, that you realise just how easy Windows is, and that Linux is indeed, for geeks.

As I said, it's a shame, because it's a nifty little device, and had it had Windows on it, I suspect there wouldn't have been the networking problems, but then it would probably have cost almost twice the price.  I'm still half tempted to try to install XP on it, but I doubt they would accept a return after that, and I don't want to go to the additional expense of buying an XP license either.

[Ted]

Linux is indeed, for geeks.

Nobody's called me a "geek" since i stopped biting the heads off chickens, but i'll take it as a compliment anyway

[Simon]

Sorry Ted, nothing personal, and no offence meant! 

I've actually made another small step this evening, after requesting an RMA from the vendors, and I have managed to get connected to the internet, but only by disabling security on the router.  Stupidly, I only disabled it on the Eee PC before.  So, after that, I have been trying all different types of passwords, from the simplest alpha numeric 8 character, to the more secure WPA-PSK 63 character ASCII passphrase that I usually use.  With security enabled, the Eee PC just won't connect.  So, it seems we have found the root of the problem, but is there a solution?

[Simon]

Oh, and to add to the above, it also works with WPA, so it's just WEP that seems to be the problem. 

[Ted]

Sorry Ted, nothing personal, and no offence meant! 

I've actually made another small step this evening, after requesting an RMA from the vendors, and I have managed to get connected to the internet, but only by disabling security on the router.  Stupidly, I only disabled it on the Eee PC before.  So, after that, I have been trying all different types of passwords, from the simplest alpha numeric 8 character, to the more secure WPA-PSK 63 character ASCII passphrase that I usually use.  With security enabled, the Eee PC just won't connect.  So, it seems we have found the root of the problem, but is there a solution?

No offence taken here Simon, just my attempt at humour (which you may recall doesn't always go strictly to plan)

My suggestion to turn wireless security off was only meant as a temporary measure, as a diagnostic for the problem.

Sorry, are you saying it works with WPA enabled but not with WEP enabled? Very strange. In the past i've had the very opposite happen beacause i didn't have WPA supplicant installed, Guess what, it didn't work even after i installed it.

[Simon]

Sorry Ted, I got it the wrong way round.  It works with the WEP, but not with WPA. 

What I was thinking is, if I can get online with WEP enabled, I wonder if there's some sort of download somewhere to fix the WPA issue?  Not being familiar with the Linux community, I wouldn't know where to start looking.