Broadband Connection Problems

  • Thread starter Thread starter Terry Bennett
  • Start date Start date
T

Terry Bennett

Can anyone make any suggestions?

I have a BT Voyager 2091 Router that I know works OK. When I first
installed it it set-up fine and I was able to connect to Broadband using
either the Ethernet cable or wirelessly.

Everything was great until I tried to install a Belkin wireless Print Server
to enable me to use 2 printers located in another room. This was fraught
with problems and several calls to the Belkin helpdesk yielded nothing. I
then made the mistake of asking the BT Broadband Helpdesk for advice and,
after a 2 hour 'phonecall they had not only failed to make any progress with
the Print Server but also managed to disable any form of connectivity
between my laptop and Broadband (either using the Voyager router or even
another Alcatel Speedtouch USB modem that I have). This seems to have been
the result of deleting some registry folders named 'Winsock' and
'Winsock2' - after that I received a Symantec message telling me that TC/IP
was not installed.

Anyway, after a couple of further lengthy calls, the TC/IP elements are now
working again and I can connect to Broadband using my Alcatel modem. The
Voyager router is, however, not connecting - the concensus from BT is that
my laptop is defaulting to the wrong IP Address (254.?.?.?, whereas I know
that the Router is set to 192.168.1.1). They suggest that this is a fault
with the Wireless Adaptor in my laptop (Intel(R) PRO / Wireless 2200BG) and
suggest that I need to 'rollback' (?) my computer by pressing F10 during
Start Up - I undestand that this restores it to 'as delivered' condition and
thereby erases all additional programmes, data, etc that I have added. This
doesn't appeal!

I appreciate that this may be a problem too involved to resolve via this
forum but can anyone point me in the right direction?

Many thanks.
 
Terry Bennett wrote:
Snip.................................

They suggest that this is a fault
with the Wireless Adaptor in my laptop (Intel(R) PRO / Wireless 2200BG) and
suggest that I need to 'rollback' (?) my computer by pressing F10 during
Start Up - I undestand that this restores it to 'as delivered' condition and
thereby erases all additional programmes, data, etc that I have added. This
doesn't appeal!

I appreciate that this may be a problem too involved to resolve via this
forum but can anyone point me in the right direction?

Many thanks.
A "Restore" does not have to take you back to "as delivered".

Start-->Help and Support choose "undo changes to your computer with
system restore" from the "Pick a task" menu.

This will allow you to pick a recent "restore point"
 
Frank. Having tried using Restore it doesn't seem to solve the problem. All
of the changes to registry settings, etc were made on Tuesday evening of
this week but even by selecting a restore point during last week I get a
message saying that no changes have been made to my PC!

Any ideas?
 
Terry said:
Frank. Having tried using Restore it doesn't seem to solve the problem. All
of the changes to registry settings, etc were made on Tuesday evening of
this week but even by selecting a restore point during last week I get a
message saying that no changes have been made to my PC!

Any ideas?
Did you try a "Restore Point" further back in time?

If you hard wire your laptop to the BT router can you connect to the
Internet?
 
Frank. I first tried one from Monday (the day before all the changes) and,
as that didn't work, I then tried one from last week but still had the same
result.

No, even using the Ethernet cable gives nothing via the router although at
one stage this did work.

I spoke to a colleague today who knows a little about computers and he
seemed to think that the 'Restore' function on XP is not much use (Norton Go
Back being better). His recommendation was to do a 'destructive restore'
which I don't much like the sound of!
 
Terry said:
Frank. I first tried one from Monday (the day before all the changes) and,
as that didn't work, I then tried one from last week but still had the same
result.

No, even using the Ethernet cable gives nothing via the router although at
one stage this did work.
When you restored your "Winsock" settings how did you do it and how did
you test that it was functional?
 
To be honest I don't know that they were restored. Somebody talked me
through re-installing TC/IP which seemed to load from XP - is that the same
thing?
 
Terry said:
That seems to have reset the Winsock directories OK but it hasn't cured the
problem.
Did you re-boot your computer before you retested?

What do you get for an IP address if you
Start-->Run type cmd press enter
type ipconfig press enter
 
Yes, I did re-start.

I get 169.254.13.154 and there's no default gateway shown either (is that
right?). The router is 192.168.1.1
 
Terry said:
Yes, I did re-start.

I get 169.254.13.154 and there's no default gateway shown either (is that
right?). The router is 192.168.1.1
Check in the properties of your network card that the "Internet Protocol
TCP/IP" box is ticked and that the card is set to "obtain an address
automatically".
 
Yes, I checked that and it is.

Frank said:
Check in the properties of your network card that the "Internet Protocol
TCP/IP" box is ticked and that the card is set to "obtain an address
automatically".
 
This is beginning to make sense. Your PC has an IP address from a
range reserved for authorized private class B network addresses
(169.254.0.1 - 169.254.255.254), with a subnet mask of 255.255.0.0,
Automatic Private IP Addressing (APIPA), XP default when it can't find
an DHCP server. First attempt would be to manually enter the DHCP
server IP then reboot the system
| Yes, I checked that and it is.
|
| | > Terry Bennett wrote:
| >> Yes, I did re-start.
| >>
| >> I get 169.254.13.154 and there's no default gateway shown either
(is that
| >> right?). The router is 192.168.1.1
| >>
| > Check in the properties of your network card that the "Internet
Protocol
| > TCP/IP" box is ticked and that the card is set to "obtain an
address
| > automatically".
|
|
 
Terry said:
Yes, I checked that and it is.
Since you will have restarted your computer recheck your ipconfig
result(use this IP instead of the 169.254.13.254) then:

Start-->Run type ping 169.254.13.254 and press enter

if it times out try

Start-->Run type ping 127.0.0.1 and press enter

if they both time out you may have a corrupt tcp/ip stack.

To reset tcp/ip

Start-->Run type netsh int ip reset c:\resetlog.txt and press enter
 
Terry said:
Thanks Mungo - how would I do that?
Where you set your network to obtain an IP address automatically instead
use "use the following address"
IP address 192.168.1.3
subnet mask 255.255.255.0
default gateway 192.168.1.1

what were your results re. Franks ping checks?
 
Frank. I have tried to ping 169.254.13.254 as suggested but that timed-out.
127.0.0.1 worked OK though (4 sent, 4 received). The reset of the tcp/ip
seemed to work as well but at the end of the day the IP Address shown when
looking at the Wireless Network Connection Status is still 169.254.13.154.
 
Thanks Rob. I have done as you suggested - assume you mean 192.168.1.3 in
the IP Address (rather than 192.168.1.1)?. I am entering this under the
Internet Protocol (TCP/IP) details rather than Microsoft TCP/IP version 6
which also shows on the list. It also asks for details of the DNS server to
be inputted but I left that blank? Anyway, still no results.
 
Back
Top