Everyone is always learning so don't feel left out.
I think the port forwarding probably isn't key to the result - if the devices are on the same subnet then port forwarding is not relevant. It may be needed for some Tivo features involving the outside world but I have none of the ports recommended by Tivo support forwarded to the device, and everything except the Tivo port configuration test works fine - that's consistent at least. Until they document in more detail what the ports are for I plan to leave it that way.
I'm not familiar with the 3102 but I am guessing it was providing the DHCP address to your PC while the NB6Plus4W was providing the address to the Tivo, and they were set up to issue addresses on different subnets. One solution would be to set them up to provide addresses in the same subnet, ie both 192.168.0 or 192.168.1 but with different starting points and ranges that do not overlap, but that's a bit of a kludge.
At the moment your PC is traversing two devices (3102 and NB6Plus4W) in order to reach the outside world. It would be better if it were one. If it was my set up I would have the 3102 and PC both connected to the router, along with the Tivo, and I would disable DHCP on the 3102. The 3102 VOIP setup might need some work - check out the link below which I think describes your situation:
http://forum.voxilla.com/linksys-sip...ter-20184.html
Restarting everything is always a good idea, otherwise the debugging process has too many variables to deal with.
Disconnecting the 3102, and plugging the PC straight in to the router was a sensible thing to try (as long as you rebooted of course as you would then need to get an IP address from the router).
I am 90%+ confident that the subnet issue was the problem as it is documented in a few places. I tried a little recabling of my setup to put the Tivo and PC on different subnets and while both the Tivo and PC could reach the outside world, and the PC could reach the web page on the Tivo (a routeable protocol) the Tivo Desktop software on the PC could not see the Tivo as it uses a multicast, non-routeable protocol only ever intended to be used on the local subnet.
Glad to hear it is working - guess you now have to wonder if the changes made will break something else. That's half the fun of networking ...
John
Bookmarks