View Full Version : Help re. wireless network plus NTL cable modem
10-21-2005, 07:22 AM
I have spent 11 hours going around in circles and no-thanks to NTL tech support, who clearly either don't know or more likely can't be bothered.
Anyway - my friend, who has an NTL set-top TV box, upgraded to TV/Telephone/Broadband package and the NTL installer put in a cable modem connected directly to the house-feeder cable from the street. Great - so far.
The modem has a standard Cat5 RJ45 connection point.
The NTL guys told me all I would need to do is plug a wireless router into the modem, wireless NIC into the PC and bob's-your-uncle!. Hmmmm, can't agree with that.
So, I have the PC wirelessly talking quite happily to the wireless router via the web interface and it is very happy.
What I DON't have is the wireless router getting out the door through the cable modem. Yes, I have checked all the router settings and no security is enabled yet, DHCP is enabled, Connection 1 username and password are exactly as from NTL.
PC is running Win2k, PC NIC is Belkin High-Speed Wireless G, wireless router is D-Link DSL-902, cable modem is NTL Home 250.
Any ideas anyone ?
10-21-2005, 08:42 AM
How have you set up the wireless router? Have you got the nic and the wireless router set up to talk to each other correctly? You cant just plug the nic in and get it to work straight away but I suppose you already know that. They both have to be set up on the same channel. You could have to spoof the MAC address of the nic card that the connection was originally set up with onto the wireless router.
I'm having a similar problem setting up a wireless router with a ntl modem. All I get is limited or no connectivity. The cable modem is plugged into the wan port on the wireless and the socket 1 is connected to the nic. This should work as the modem works on its own with the nic. Have no idea why this is happening either.
10-21-2005, 09:04 AM
Yep, both on same channel and quite happily chatting away to each other.
I was told that cable modem should NOT be in WAN port, only in one of slots 1-4 of the switch.
I thought at first that the modem might only like one MAC address and that the router was also putting out a MAC address along with the PC, however if the PC is just routing through (the router) then all the modem should see is the PC MAC address - I've never known a router to add its MAc address to the MAC addresses of any equipment plugged in to it.
Sounds like we have a very similar probelm but no enlightening solutions.
Sometimes I really hate computers.
10-21-2005, 10:28 AM
You are right that the connection is going through the router but that will have it's own MAC address as well. If the modem connects to the router and finds the wrong MAC address then it will stop there. This is what I have just found out from a collegue at my work. I'm going to spoof the MAC address of the NIC on the router to hopefully solve my problem - it might work for you too.
The person who told you to not plug it in the WAN port is a plonker. If you plug it into the LAN ports then the connection will deffinately not go anywhere - this could be your problem also!
10-21-2005, 10:39 AM
I'll try the WAN port.
Let me know if the MAC address spoof works for you.
Best of luck.
10-21-2005, 11:35 AM
Ok will do =)
10-27-2005, 03:51 AM
Well, I reset the linksys wireless router and it then would allow the connection to go though (even though I had tried this already!) The wireless router is just acting as a normal router. It wont do wireless so I think that it's faulty. I'm going to buy a better quality netgear wireless router and I bet that will work straight away!
How did you get on with yours?
10-27-2005, 09:29 AM
may sound strange but it is probably the answer. are you using a cross over cable or standard?
10-27-2005, 09:41 AM
I'm using a standard cable. You're not supposed to use a cross over cable. This should't affect the wireless router giving out its transmission which is why I think it's the router itself.
10-27-2005, 01:02 PM
that was actually more for charlieatlas.
for your issue, it sounds like a bad router.
10-31-2005, 04:45 AM
Whoops! Yeah that's what I thought, cheers Keith0 =)