Cable Forum - View Single Post - why is it that when I need to phone VM, they fail to deliver?

Tech_Boy · 10-10-2009, 11:14

if the OP's router mac address has been cloned, then that has absolutely nothing to do with Virgins T&C's only if some joker had cloned the Modems mac address would there be a breach of the T&C's, and the OP would get either intermittent or no service at all, as the other modem vied with his for connection.

As Moldova has said, the connection works when connected directly to the PC, so as far as the llimits of Virgins support scope goes all is fine.

Virgin cannot be held responsible for what happens with 3rd party equipment & people messing around & changing mac addresses on their equipment, or manufacturing errors causing multiple devices to be sent out with the same mac address. As happened on alot of XP machines when the generic drivers for the onboard nic were used instead of the manufacturers supplied drivers.
There was a list of affected Mac addresses kicking around the knowledgebase, before the dark times,... before the Merger.

10-10-2009, 11:14	#17
Tech_Boy Inactive Join Date: Mar 2004 Location: Swansea Age: 49 Services: Inhumations, for the right price Posts: 517	Re: why is it that when I need to phone VM, they fail to deliver? if the OP's router mac address has been cloned, then that has absolutely nothing to do with Virgins T&C's only if some joker had cloned the Modems mac address would there be a breach of the T&C's, and the OP would get either intermittent or no service at all, as the other modem vied with his for connection. As Moldova has said, the connection works when connected directly to the PC, so as far as the llimits of Virgins support scope goes all is fine. Virgin cannot be held responsible for what happens with 3rd party equipment & people messing around & changing mac addresses on their equipment, or manufacturing errors causing multiple devices to be sent out with the same mac address. As happened on alot of XP machines when the generic drivers for the onboard nic were used instead of the manufacturers supplied drivers. There was a list of affected Mac addresses kicking around the knowledgebase, before the dark times,... before the Merger.