invalid mac

[clio1]

Originally Posted by helpfull

I'm having to do it between 2 houses as I don't have cable. I didn't reset after loading the "Official Firmware". I'll follow your instructions tomorrow.
As I said in an earlier post we definitely got one working before and I would have thought if it was terminal then it just wouldn't come back on whatever we did. So I certainly believe you Lincsat.

Well im sure if you cant get is working, lincsat, as a supplier of said boxes would take it back and get it sorted for you as a good will gesture, as all he has to do is return it to manufacturer and he will get a replacement one.

[lincsat]

The message on the box was "INVALID MAC", nothing about a cert. That is the only message of that type that I have seen. Are you saying that there is a different error common on the boxes?

I don't know how the box authenticates on the server and TBH, I don't want to get too close to the server side. All I know is that it was suggested to me that loading the official firmware would work - then when I tried it, it did work.

[lincsat]

Originally Posted by clio1

Well im sure if you cant get is working, lincsat, as a supplier of said boxes would take it back and get it sorted for you as a good will gesture, as all he has to do is return it to manufacturer and he will get a replacement one.

If I supplied the box and it's under warranty, then of course I will return it. They do swap them over just takes a little time. I would try the firmware fix first though.

[helpfull]

[QUOTE=clio1;591509]What the heck are you on about m8, watch my mouth, for what excatly? ? Becauce i said i got the info from the horses mouth, i suggest you read the post correctly before putting your mouth in gear, or your fingers for that matter
QUOTE]

lol I didn't say "watch your mouth" I was trying to be funny but it obviously didn't work.

Lets not let this go any further obviously a misunderstanding.

Back on topic. I'm sure you know what your talking about Clio. I'm also sure Lincsat does too.
Is it possible for the Eeprom to be corrupted and then right itself? Or is it read only.? I'm pissing in the wind here because it's not a field I have any knowledge in. I'm just thinking that both of you are correct to an extent so there may be 2 problems with the same visible result 1 fixable and 1 not.
RE sending boxes back. I can do that myself.

[clio1]

Originally Posted by helpfull

but I'm off the opinion that it's either a bad flash or a problem with the Mac on certain Modems.
A bit of research and it could be a couple of things.
1. Some Modems do not recognise Macs that don't begin 00
2. Some Modems will not allow non permitted Macs access.

Going by his post obliviously there must be two, so that could have been the one you had, and when you reflashed it worked for you, the other Invalid mac is the cert that allows to connect, if its the latter no amount of flashing will fix this, and means a replacement box, "REGARDLESS" of it been in warranty or not, as this is a known fault on some boxes, so actually any supplier could take it back and replace it for them.

[helpfull]

Tried and failed ;-( So with regard to this box Clio was right.

What I cant understand (maybe you'll know this Clio) how come I get the "invalid mac" message when the box isnt connected to the ethernet cable? I would have thought the message would come after trying to access the server and receive a return message "Invalid Mac" Does that make sense?
How does the box know it has an invalid mac until the server tells it.?

[gadgetfiend]

Has the KV previously been connected to the network on current f/w ? if so the box may only be reporting this message as it now knows that the mac is invalid from the last time it sought network authorization. Dont know for sure though but seems logical to me.

[QinteQ]

A guess .. ..

Because the EEprom writer will have more than several lines of error code to do with its capacity to validate contact with the ' mothership ', one of those lines will be the simple 3W handshake ' protocol. So lets say there are 10 [ different ] lines of code they would all result in the [ same ] print / display routine of "invalid mac". It would be invalid because it does not exist.

[waqasahmed]

Originally Posted by helpfull

Tried and failed ;-( So with regard to this box Clio was right.

What I cant understand (maybe you'll know this Clio) how come I get the "invalid mac" message when the box isnt connected to the ethernet cable? I would have thought the message would come after trying to access the server and receive a return message "Invalid Mac" Does that make sense?
How does the box know it has an invalid mac until the server tells it.?

I'm making an assumption here, but it's possible that KV has been lazy and re-used your MAC address, meaning that you're being kicked off from the server