Been working on it 24 hours now with support from HP leading nowhere.
I spent 3 hours last night waiting for a verizon tech and another 30
minutes so far today. In the process i managed to check my firmware
in my MI424-WR Actiontec router from Verizon from
4.0.16.1.45.160 to
4.0.16.1.55.0.10.4.3

I have found lots of posts on problems with this router but a) no
satisfying answers and b) not much specifically about Vista
compatibility problems.

I have noticed some strange messages in the router logfile that appear
to come from this computer trying to get an IP address.

This is the oddest one:
kern.debug New IGMP type=34, why we do not know about it?

But I am also seeing LOTS of these messages filling up the log:
daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.

daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.

"You are having the same problem" is not a good description of what
issue you are trying to resolve. Please post a complete description
of the problem. Also post information on what network card you are
using and what driver.

On Sun, 2 Dec 2007 08:15:10 -0800 (PST), Steve Quatrano
wrote:

Been working on it 24 hours now with support from HP leading nowhere.
I spent 3 hours last night waiting for a verizon tech and another 30
minutes so far today. In the process i managed to check my firmware
in my MI424-WR Actiontec router from Verizon from
4.0.16.1.45.160 to
4.0.16.1.55.0.10.4.3

I have found lots of posts on problems with this router but a) no
satisfying answers and b) not much specifically about Vista
compatibility problems.

I have noticed some strange messages in the router logfile that appear
to come from this computer trying to get an IP address.

This is the oddest one:
kern.debug New IGMP type=34, why we do not know about it?

But I am also seeing LOTS of these messages filling up the log:
daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.

daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

I don't know if this is the problem, but go here for a link that has
others working better with the MI424-WR/ FIOS and Vista...
http://www.dslreports.com/forum/r195...om-FIOS-Answer

---
Jeffrey Randow

Windows Networking MVP 2001-2006
http://www.networkblog.net

On Sun, 2 Dec 2007 08:15:10 -0800 (PST), Steve Quatrano
wrote:

MI424-WR

also, see if
http://support.microsoft.com/default...b/939006/en-us helps

On Sun, 2 Dec 2007 08:15:10 -0800 (PST), Steve Quatrano
wrote:

Been working on it 24 hours now with support from HP leading nowhere.
I spent 3 hours last night waiting for a verizon tech and another 30
minutes so far today. In the process i managed to check my firmware
in my MI424-WR Actiontec router from Verizon from
4.0.16.1.45.160 to
4.0.16.1.55.0.10.4.3

I have found lots of posts on problems with this router but a) no
satisfying answers and b) not much specifically about Vista
compatibility problems.

I have noticed some strange messages in the router logfile that appear
to come from this computer trying to get an IP address.

This is the oddest one:
kern.debug New IGMP type=34, why we do not know about it?

But I am also seeing LOTS of these messages filling up the log:
daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.

daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/