Wireless doesnt work. Wired does.

[MAllen]

Interesting.... RM CC3 - no idea what that is. But this also points towards the excuse for an isolated test of the DLink APs and the Dells. i.e. is it your network infrastructure causing the problem, or the combination of DLink and Dell?

 

[BoomAM]

Yep - I hear you on that one. But you also say that you cannot ping anything except for 127.0.0.1. At the very least, if you are genuinly connected, you should be able to ping the AP from the laptop.

I know. Its wierd. Every software app report it as connected & as having a valid IP. But it cant ping anything.

...This sounds very similar to what you are seeing.

Ordinarily, i'd agree. But the key is just a series of numbers from, for example 01 to 16 or whatever. Theres nothing complex, or to get wrong, about the keys, and ive inputted them several times now.

I wasn't ignoring your comments about being connected. I just don't 100% trust the computer to tell us. Especially as it can't ping the AP. And your valid IP Addresses are ones you have entered, so they are valid - but they are not conencted to the network.

Dont worry about it.

I intend to try DHCP, AP keys, the AP isolated, and UbuntuLive when im next in.

How come RM aren't installing the wireless stuff? RM install alsorts of stuff on there servers so I would suggest you take the problem to them

When i got there, these 3 AP's were just lying around. I was asked that if i had the time between other things to sort them out. So i did. And it worked fine, and they were installed in places that i told them to install them (little to no surrounding metal to minimise the faraday effect on the signal).
Anyway, i got in after xmas and was told by the other techy that RM said that the Laptops should automatically jump between AP's depending on signal strength, but they wouldnt. So i had a look, and that led me to this problem.

Them may and charge you there callout rate but that the buggers they are.

If you cant tell I work for a competitor to RM. We hate them

We hate them too. They're software sucks.
AFAIK, we're looking at changing from RM to another well known company soon.

Interesting.... RM CC3 - no idea what that is. But this also points towards the excuse for an isolated test of the DLink APs and the Dells. i.e. is it your network infrastructure causing the problem, or the combination of DLink and Dell?

Research Machines Community Connect 3.
Most schools/colleges/uni use RM based networks. Its essentially a collection of software thats run on the server & client PCs that make them uber-secure. Not to mention uber-annoying to fix problems. Google it.
The theory is, that if you have a problem that you cant fix, you ring them, and within a week or so, they ring back with a fix. Problem is, that they're not all that good. Their field engineers are good though.
Its annoying installing software. Its not as simple as installing it on each machine. Or if its a network installer, running that and letting it install it on multiple machines. 'Packages' need to be made and then allocated, and that takes time, because the package building machine needs to be rebuilt for each package, and all manor of errors can & do occur.
Before looking into this wireless problem, it took me almost 2 months to get Cubase working properly on the network.

 

[benjo plz.]

Research Machines Community Connect 3.
Most schools/colleges/uni use RM based networks. Its essentially a collection of software thats run on the server & client PCs that make them uber-secure.

Secure? yah right, that didn't stop CS 1.6 and UT GOTY being put on the network within a month of CC3 being installed. Only really secure thing is Securus.

 

[BoomAM]

With the right permissions and the known RM backdoors, most parts of CC3 can be circumvented. But on a high school network, its bulletproof. A little too bulletproof.

 

[benjo plz.]

CC3 isn't bulletproof by a long way. Theres a backdoor that allows files to be placed and run in the C:\Program Files folder that cannot be removed.

 

[MAllen]

LOL - I guessed that "RM" was Research Machines. I worked for them once during the summer of 1989. Was installing a new database system in the Support Department. Entering the data into it, etc. I was there as a temp, and as I was leaving I explained to my "supervisor" that he was soon to be out of a job. That computer system I was putting in was about to put him out of work.

Maybe this RM CC3 system is logging the MAC addresses of machines that should be on the network, and therefore blocking all of your new Dells as they are not seen as kosher kit?


Oh - and another suggestion. When you are trying your experiments next week, have a large lump hammer near by. I often find this helps to "persuade" equipment to work correctly......

(Actually this is advice I usually give my customers. I live in Brighton, so I tell them to go down the sea front and buy an inflatable hammer. Ideal for hitting computers and people with when things go wrong. )

 

[BoomAM]

Maybe this RM CC3 system is logging the MAC addresses of machines that should be on the network, and therefore blocking all of your new Dells as they are not seen as kosher kit?

Nope.
Ive never 'registered' the MACs of anything on the network while ive been there and its all worked fine.

CC3 isn't bulletproof by a long way. Theres a backdoor that allows files to be placed and run in the C:\Program Files folder that cannot be removed.

This thread isnt about arguing the merits of CC3. Make another thread for that. Im not interested in arguing about CC3 at the moment, merely fixing the problem that im having.