[Merged] Connection problem - IP address 169.
08-07-2004, 10:24
|
#1
|
Inactive
Join Date: Jan 2004
Posts: 13
|
everytime i start pc i have to reboot stb?
Hi, its been getting on my nerves for ages dont want to call tsb because at least i have a connection and i know its only a petty thing lol! But i Have Win Pro on a Dell pentium2 450mhz with 192mb memory  (i Know i hear fits of laughter !!! but it does me for what i want!) But everytime i start my pc i get an i.p. of 169.xx. Its just a pain in the butt having to go downstairs after putting my pc on upstairs to reboot the stb which is a ditv 1000 box, then everything works fine. The weird thing was i installed broadband medic the other day, and since then i seem to have about 96% success of connecting to BB without rebooting stb first?! The one time i did have a problem i ran bb medic and it said network card failed - it is a 3com 3c905tx, but again was ok after reboot? Anyone any suggestions please - need new NIC even? Cheers folks
|
|
|
08-07-2004, 10:47
|
#2
|
cf.mega poster
Join Date: Jun 2003
Location: Warrington ntl:81304 Altitude: 12m (and falling)
Posts: 4,499
|
Re: everytime i start pc i have to reboot stb?
Some possible reasons for your 169 address are listed here:
http://homepage.ntlworld.com/robin.d...dip.html#ip169
|
|
|
09-07-2004, 00:51
|
#3
|
Inactive
Join Date: Jan 2004
Posts: 13
|
Re: everytime i start pc i have to reboot stb?
cheers will have a look through
|
|
|
09-07-2004, 12:31
|
#4
|
Inactive
Join Date: Jun 2003
Location: Middleton North West Manchester
Services: up to 30 MEG CF version of Peter Kay
Posts: 1,871
|
Re: everytime i start pc i have to reboot stb?
Check your firewall is allowing your connection to refresh its lease
here
also ditch BB medic  Ditv for BB 1000 box  2000  4000  samsung have not played with one yet any offers
|
|
|
09-07-2004, 13:57
|
#5
|
Inactive
Join Date: Jul 2004
Posts: 11
|
Connection problem - IP address 169.
Hello all
I need help, at the moment I cannot connect to the internet although everything looks normal correct lights on STB and USB light as normal, in internet options it shows my connection as being connected but the IP address is a 169. (not getting IP from NTL)
Now just to give a bit of history I had this problem a few months ago and NTL could not work out the problem and after numerous visits and new set top boxes they said they could not find a problem so it must be my pc, I clean installed my pc which is a dell/xp and the problem was still present, I was booked in for another visit however before they could come out again it came back on as if by magic. (I found out online there was some NTL maintenance being carried out relatively near - so I put it down to that even though NTL said it wasn't their problem).
(At the time of this loss of service I was downloading an Mpg file with did not work and I got a server reset message from the target server and the download stopped - this happened twice but after the first time I had no problem with NTL)
I am at work so can't really try anything at the moment but any suggestions will be welcome, as I don't want to go through the hassle I went through last time only for it to come back on without anything changing.. There is something online about service outage but as of last update 7th july my area is not mentioned  Thanks in advance.
|
|
|
09-07-2004, 14:03
|
#6
|
Inactive
Join Date: Jun 2003
Location: Surrey
Age: 58
Services: Virgin stuff
Posts: 6,407
|
Re: Connection problem - IP address 169.
I had this happen last night to my son's pc ....
Go to Device manager, via My Computer ... properties.
Find your USB connection and remove it.
Reboot, the PC will refind the USB device and reinstall drivers.
All should work from then ...
Not sure what the problem actually is, wheteher it is NTL or the modem, but that fixed it for me (although I use Ethernet cards).
|
|
|
09-07-2004, 14:18
|
#7
|
Inactive
Join Date: Jul 2004
Posts: 11
|
Re: Connection problem - IP address 169.
Thanks Nemesis, I will try that if I still have problems when I get home, the nationwide maintenance is now reported as complete so possibly the problem may have gone.
Thanks again
|
|
|
09-07-2004, 14:55
|
#8
|
Inactive
Join Date: Jun 2003
Location: Middleton North West Manchester
Services: up to 30 MEG CF version of Peter Kay
Posts: 1,871
|
Re: [Merged] Connection problem - IP address 169.
suggest you go to NIC card and ditch the usb it tends to use far to much pc memory resources and that cause the timeouts
|
|
|
09-07-2004, 15:02
|
#9
|
Inactive
Join Date: Jul 2004
Posts: 11
|
Re: [Merged] Connection problem - IP address 169.
Yes, I was on NIC when this problem occurred the first time and the NTL engineer switched me to USB (clutching at straws trying to find a solution) then after it fixed itself I kept it as it was. (didn't want to disrupt it back when it was working)
|
|
|
09-07-2004, 15:03
|
#10
|
Inactive
Join Date: Jun 2003
Location: Surrey
Age: 58
Services: Virgin stuff
Posts: 6,407
|
Re: [Merged] Connection problem - IP address 169.
Well as theEng says, Nic would be better, so switch back anyway
|
|
|
09-07-2004, 15:06
|
#11
|
Inactive
Join Date: Jun 2003
Location: Middleton North West Manchester
Services: up to 30 MEG CF version of Peter Kay
Posts: 1,871
|
Re: [Merged] Connection problem - IP address 169.
NTL and engineer,  NTL and engineer  hmm no NTL and tech
|
|
|
09-07-2004, 19:53
|
#12
|
cf.mega poster
Join Date: Sep 2003
Posts: 12,047
|
Re: [Merged] Connection problem - IP address 169.
get SACM
|
|
|
09-07-2004, 20:06
|
#13
|
Inactive
Join Date: Jun 2003
Location: Middleton North West Manchester
Services: up to 30 MEG CF version of Peter Kay
Posts: 1,871
|
Re: [Merged] Connection problem - IP address 169.
Quote:
Originally Posted by Chrysalis
get SACM
|
or a samsung box
|
|
|
15-07-2004, 23:17
|
#14
|
Inactive
Join Date: Jul 2004
Posts: 4
|
Re: [Merged] Connection problem - IP address 169.
Long story but bear with me - I need help!
Have had NTL broadband for a year via a set top box. The wall socket was in a separate room, linked by RJ45 cable plugged into the LAN Ethernet port on our Mesh computer running XP. Oldest son took the Mesh to University, and we replaced it with an Evesham (XP again)- it just plugged and played straight away on the ethernet NIC. Son came home and tried to install a Netgear DSL router to share the broadband connection.
For reasons of his own, he decides that he doesn't read\need router install instructions, doesn't keep a note of the MAC or IP address and sets up everything, (router and two PC's) while the set-top box is still switched on. He also decides to set up his PC as the administator. Later he tells me that when tried to plug the broad-band connection into his PC it didn't work then, so he just plugged it back into ours.
Anyway router fails to initialise and the set-up wizard aborts. Son then decides to manually configure everything, and plays with settings, (but keeps no record of what). By the time I get home, the only option appears to be get everything back to the pre-install state. Neither machines has the router software as the wizard was aborted and the manual config never achieved anything. So I turn off the Evesham, turn off the set-top box, unplug the cables that came with the router and re-attach the RJ-45 to the wall socket and the LAN port. Fire her up and hey presto.... private IP address and no broadband connection. Same on the Mesh. Okay,go for a system restore point some three weeks earlier, (oh, did I mention he didn't take a system restore point). Nothing. Ring NTL technical support line, go into multiple checks, - ipconfig release, ipconfig renew, turn off DHCP, turn off DNS, turn them on, disable the network card drivers, re-enable them, all with re-boots of PC and set-top box. The NTL people assure me they can ping all the way to the network card. Then NTL want me to re-install XP (I haven't yet) but then they say both network cards must be dead\faulty.
So I set up peer to peer network, using the RJ45 cable and the LAN ports on both PC's. The Mesh accesses the printer via the Evesham. The Evesham accesses the re-instated dial-up on the Mesh. I use internet sharing and the Microsoft small network facility in XP. NTL get me to try some DOS command that will restore everything to the original factory settings for the Evesham after I've removed the ICS\network. Still no joy. I phone up customer services - can the PC (Evesham)be plugged directly into the set-top box. Plug in, hooray, a welcome to NTL world screen, and then nothing, it hangs for forty minutes while I sit in NTL's call centre queue. I give them an ultimatum, mend it or take it away. They'll get an engineer out.
Engineer arrives and he can't get an IP address or connection. Eventually replaces much of the wiring and all of the leads until signal obtained. Plug new RJ45 cable into the back of the Evesham, power up set-top box, power up PC and....private IP address. I'm referred back to the Technical help-desk.
Meanwhile, I discover that installing a Netgear router on NTL broadband is not for the computer novice. I get referred to Robin Walkers web-pages on NTL BB problems, but the router has gone back to the supplier, and as it never installed properly, so a lot of the other stuff there doesn't seem to apply. Is it a virus or some form of denial of service. Well - we haven't got a virus checker, (son has Norton on his MESH),as knew we were getting the router, and I'd heard that both Norton & McAfee can cause problems with router installation, plus routers usually come with a firewall that is every bit as good. Using dial up I've been to both the Symantec and McAfee web-sites and used their free scanners, but neither found anything. Spybot and WinPatrol are installed on the Evesham.
All subsequent system restores to earlier points have failed since that first restore. I've tried to write our files to CD's, but both the DVD\CD writer, and the ordinary CD writer aren't working.I've not had cause to use them before for this purpose, so both may never have worked as writers.
Any suggestions - I'd love to go to another broadband supplier but if its a PC config or Denial of Service then we could still have the same problem.
|
|
|
15-07-2004, 23:47
|
#15
|
cf.mega poster
Join Date: Jun 2003
Location: Warrington ntl:81304 Altitude: 12m (and falling)
Posts: 4,499
|
Re: [Merged] Connection problem - IP address 169.
I suspect this started because you (he?) has changed the MAC address of the device talking to the STB. Have you found this page?
http://homepage.ntlworld.com/robin.d...tips/swap.html
|
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT +1. The time now is 04:59.
|