Johnnyd,
One other thing I should mention. I have tried connecting 2 distinct PCs direct to the Cable Router. One is a laptop using Windows Vista - eventually the Virgin IP address is picked up (82.....) but on my regular machine (Windows 2000 Pro) the Virgin IP address is NOT picked up (defaults to the Microsoft 169.. address). Neither works via the wireless router which was working OK a week or so ago (occasionally the WR gets a 192.168.100... address which is NOT in the range specified for anything configured on it - i.e. the local lan).
Now I am quite prepared to admit that my WR might be playing up but I think it TOO much of a coincidence that...
1. You have 2 WRs not working.
2. I have a Windows2000 PC which also is having issues getting the Virgin DHCP allotted address direct from the cable router.
I really don't know if VM have tweaked their DHCP so that things stop working (for some WRs and Win2000) but that is my guess - and I am a professional network person. Unfortunately there is no easy way of discovering what is going on as VM "Support" just tell you to reboot the CM (yeah, as if we haven't already tried that multiple times) or if you are lucky replace the thing (and it still gives problems).
Pete.
---------- Post added at 11:34 ---------- Previous post was at 11:00 ----------
Harmitage,
Whilst I would agree that on the face of it that our WRs are responsible. The factors mitigating against this are:-
1. The Wireless router has a LAN side (wireless) and a WAN side (wire). It is NOT the wireless LAN which is not working (my PCs are quite happily getting local lan addresses AND I can use the wireless lan to talk to the WR (configuration) itself. The problem is on the WAN side (to the Cable Router) which is hard wired and the Virgin DHCP address is NOT being supplied by the CM. So I don't think it is an issue with wireless interference.
2. Even with a direct connection to the cable-router one of my PCs (running Windows2000 though this might just be a red herring) isn't getting the Virgin DHCP supplied address whilst another one is. Is it likely that so many devices are having issues getting the DHCP address? I don't know.
Pete.
---------- Post added at 11:59 ---------- Previous post was at 11:34 ----------
All,
Sorry to bug everyone but there may be a solution in the following article:-
http://www.digitalspy.biz/forums/sho...php?p=11916968
I am going to try a few things this evening in light of what the article says (the clone MAC address bit). If it works I'll post. The original problem in the article mimics 100% what I am seeing - even down to the IP addresses!
Pete.