Fios YouTube Problem

[jinjuku]

I did Step 2 first with my laptop and got stuck at #12. The D-Link page was telling me that if I changed the IP address of the router I would have to change the IP address in the browser in order to access the router ... or something like that. This time it did not take me back to the log in page as it had done in #8. Entering 192.168.0.1 didn't work so I tried entering the new Router IP Address of 192.168.1.200 into the browser but that didn't work so I'm stuck at #12 and not able to log back in.

Go to start> in the run dialog type 'CMD' (no quotes) and click 'OK'.

A black screen comes up. In it type 'ipconfig' (no quotes) and hit enter. Post the output back here.

Alternately we can multi-home the network adapter:

Start>My Computer (RIGHT CLICK) and left click 'OPEN'. New window appears. Right click on 'Network' and left click on 'Properties'.

A new window will appear. Left hand side click 'Change adapter properties'. You will assign multiple IP addresses (multi-homing). I always do this PRIOR to changing network schema so no matter what I can fire up the interface of what ever I am working on.

You will assign your target (future) IP Schema to the main properties. You will click on advanced and assign the OLD network.

 

[Alex2507]

Go to start> in the run dialog type 'CMD' (no quotes) and click 'OK'.

A black screen comes up. In it type 'ipconfig' (no quotes) and hit enter. Post the output back here.

First of all I tried to do that on my Vista laptop and there was no there was no 'run' thing. With the XP desktop I was able to do as instructed but there was writing on that black screen so I peed my panties a little but just went forward and what came back looked something like this:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix: home
IP Address: 192.168.1.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1

Alternately we can multi-home the network adapter:

Start>My Computer (RIGHT CLICK) and left click 'OPEN'. New window appears. Right click on 'Network' and left click on 'Properties'.

A new window will appear. Left hand side click 'Change adapter properties'. You will assign multiple IP addresses (multi-homing). I always do this PRIOR to changing network schema so no matter what I can fire up the interface of what ever I am working on.

You will assign your target (future) IP Schema to the main properties. You will click on advanced and assign the OLD network.

I didn't do any of the above and I wouldn't know what to assign as a multiple IP address. My point of reference with those instructions is lacking but I don't think you intended me to go that route anyway.

 

[Lordhumungus]

Try 192.200.200.250 which is what we changed the static IP address to in step 7.

 

[Alex2507]

Try 192.200.200.250 which is what we changed the static IP address to in step 7.

I think I did try that earlier but it didn't work and for sure it's not getting me from here to there now.

 

[Lordhumungus]

Try

192.168.1.1
192.168.1.2

 

[Alex2507]

Try

192.168.1.1
192.168.1.2

192.168.1.1 takes me to the Westell Router

192.168.1.2 doesn't do it either.

 

[Lordhumungus]

I think that's your problem. You shouldn't be connected to the Westell router at all, even wirelessly with the same PC you are physically connected to the D-link with. I think their IPs are overlapping.

Edit: This relates to the initial setup only, so don't let that scare you for what it means in the future.

I have to go to work now, so I won't reply for at least an hour. I've sent you a PM.

 

[STRONGBADF1]

I'm over here nervous as a long tail cat in a room full of rocking chairs and you're making jokes. Your sense of boundaries really leaves something to be desired.

Boundaries???

 

[jinjuku]

192.168.1.1 takes me to the Westell Router

192.168.1.2 doesn't do it either.

You need to get to the advanced tab and add the additional network/s.

example would be:

IP Address: 192.168.200.50
Subnet Mask: 255.255.255.0

Don't bother with Gateway.

You shouldn't be seeing the Westell.

You should cable from house into Westell. Then WAN on the Dlink into the LAN on the Westell. So the Westell 'bridges' the Dlink into the cable entering the house.

You should only see the Dlink interface.

 

[Alex2507]

You need to get to the advanced tab ...

The advanced tab of what?

Left hand side click 'Change adapter properties'.

The pic's you link don't quite look like anything I can pull up on either of my computers. I've got Vista and XP but nothing quite works the way you're saying it does on either machine? What OS are those images from?

Nothing I can find on either machine has that menu on the left saying 'Change Adapter properties'.

Then WAN on the Dlink into the LAN on the Westell.

You should only see the Dlink interface.

I'm not sure how far back you read but the Westell is VDSL with a MoCA connection that I do need to be operational and LH specifically said not to use WAN on either router.

It is imperative that the ethernet cable goes from a LAN port on the Westell to a LAN port on the D-link. NOT, I REPEAT NOT, to or from the WAN (Internet) port of either device.

LH,

Disconnecting the laptop from the Westell wireless and only having it connected to the D-Link's LAN didn't help me with the various 192.xxxxxxx numbers to get back into the routers menus.

 

[Lordhumungus]

You need to get to the advanced tab and add the additional network/s.

example would be:

IP Address: 192.168.200.50
Subnet Mask: 255.255.255.0

Don't bother with Gateway.

You shouldn't be seeing the Westell.

You should cable from house into Westell. Then WAN on the Dlink into the LAN on the Westell. So the Westell 'bridges' the Dlink into the cable entering the house.

You should only see the Dlink interface.

This is actually incorrect as he can't use the Westell in bridged mode without breaking his FiOS TV services. Instead he is using the D-link as a Wireless Access Point and the Westell is retaining routing functions. As such it's LAN to LAN.

 

[jinjuku]

The advanced tab of what?



The pic's you link don't quite look like anything I can pull up on either of my computers. I've got Vista and XP but nothing quite works the way you're saying it does on either machine? What OS are those images from?

That is only due the fact that MS hates to keep UI conformity between OS releases. Always changing where the furniture is for it's blind users that MS is.

Go to Techinline Remote Desktop. Install the control and post back the Client ID #. I can take over the machine and add the needed networks in.

Fixme.it is easiest with Google Chrome BTW. If Firefox you will restart Firefox when prompted.

 

[jinjuku]

This is actually incorrect as he can't use the Westell in bridged mode without breaking his FiOS TV services. Instead he is using the D-link as a Wireless Access Point and the Westell is retaining routing functions. As such it's LAN to LAN.

Alright so the Dlink is to be used in AP only mode (if it has such a function). I know Belkin puts that in to their product.

 

[Lordhumungus]

Alright so the Dlink is to be used in AP only mode (if it has such a function). I know Belkin puts that in to their product.

In reading through the manual of the D-link I didn't see such an option specifically called out. I did some research and the instructions I posted should get him to where he needs to be as far as it being a WAP, unless I have missed something.

As a side note, b00000 Belkin. That miserable company wasted 6 months of my life trying to get their original draft-N router to work correctly after 5, yes 5, RMAs. I will never buy another Belkin product.

 

[jinjuku]

As a side note, b00000 Belkin. That miserable company wasted 6 months of my life trying to get their original draft-N router to work correctly after 5, yes 5, RMAs. I will never buy another Belkin product.

That is me and TrendNet. Never again. I have sworn off their bug ridden product lines forever.

 

[Alex2507]

Go to Techinline Remote Desktop. Install the control and post back the Client ID #. I can take over the machine and add the needed networks in.

My technofear is on full alert with all that downloading and posting my Client ID number here. I'm going to give LH a shot at getting me from here to there. He seems to have an insight into what this configuration needs regarding that MoCA connection and I've been able to follow his directions easily enough until step 12 of course. I'm worried about opening another can of worms with you taking over my machine/s. If my girl loses cable because of something you do, it's curtains for me.

 

[jinjuku]

My technofear is on full alert with all that downloading and posting my Client ID number here. I'm going to give LH a shot at getting me from here to there. He seems to have an insight into what this configuration needs regarding that MoCA connection and I've been able to follow his directions easily enough until step 12 of course. I'm worried about opening another can of worms with you taking over my machine/s. If my girl loses cable because of something you do, it's curtains for me.

I only do this for a living... You can PM the client id to me. Seriously I should be about 10 minutes and done.

Basically your Dlink needs to have it management IP address changed over to something compatible with your current network and it's DHCP server disabled. That is it in a nutshell for making a Wireless router behave like a wireless access point.

 

[Alex2507]

I only do this for a living... You can PM the client id to me. Seriously I should be about 10 minutes and done.

Basically your Dlink needs to have it management IP address changed over to something compatible with your current network and it's DHCP server disabled. That is it in a nutshell for making a Wireless router behave like a wireless access point.

I appreciate the offer but I want to take the steps and make the changes for this fix from documented instructions that I can follow and look back on like BSA's instructions on how to do screen shots. Yep, I had to look back on them to figure out how to post this.

I need to give this thing a rest for a bit but my next step is to try following LH's instructions from this Vista laptop disconnected from the Westell and hardwired to the D-Link ... but first a break.

 

[Lordhumungus]

Jin,

I just wanted to say thank you for giving me some ideas that are helping me re-think my approach to make this as painless as possible for Alex. If I understood your post correctly, I agree that one of the problems is he is no longer on the same subnet as the router and I believe this is because we disabled DHCP. While we can solve this problem by going static, I think the best approach here is to simply disable DHCP as the last step to avoid this issue altogether.

 

[jinjuku]

Jin,

I just wanted to say thank you for giving me some ideas that are helping me re-think my approach to make this as painless as possible for Alex. If I understood your post correctly, I agree that one of the problems is he is no longer on the same subnet as the router and I believe this is because we disabled DHCP. While we can solve this problem by going static, I think the best approach here is to simply disable DHCP as the last step to avoid this issue altogether.

Close. There are two possible scenarios on integrating routing equipment out of the box:

1. Is they are BOTH on the same subnet.
A. They either have the same default management IP (collision)
B. They have separate management IP (OK)
C. They have DHCP turned on
1. Possible same scope distribution (possible client collision)
2. They have complimentary scopes allotments (OK)

The first thing to always do is get the vendor documentation together on the OOB defaults and plan accordingly.

If on separate subnets you simply statically assign two IP address to the network card (multi-homed adapter) and connect the non-routing device to the routing device, plug in your computer, adjust the non-routing device to be compatible on the piece that needs to perform the routing and disable it's DHCP server. Layer two doesn't care how many subnets you have so no problem having two routers plugged into a common LAN port.

If you pick up two devices that have the same subnet and therefore managment IP you will configure a static on the computers adapter. Connect to the device to be configured as an AP and simple change it's IP and disable DHCP. Then plug into the LAN on the routing device.

The point behind having the computer statically assigned with addressing is if you don't remember if you applied settings you can still try the old address to get back to the router you need to modify.

The issue with DHCP and turning it off last is that your computer isn't going to pull two difference DHCP assignments. It is imperative that you statically assign and potentially multi-home the adapter. Trust me it is easier in the long run and you are not left scratching your head on which network assignment you leased.

With static addressing you know what networks you are on. In Cisco parlance you are on a multi-armed (as in an octopus) configuration.