Liverpool FC Forum

Posted: **Sun Nov 30, 2008 9:22 pm**

Leon i had the same problem a few weeks ago my internet provider was Aol an theyd been bought out by carphone warehouse an the ip address i was using wasnt recognised with them as mine was Buffalo . I phoned a lad an he gave me some numbers to type in an when it came up go to a thing called WAN. i got my new username and password from AOL and typed it in an applied it an it was sound. Just phone your internet provider an theyll tell you why its not being recognised,

Posted: **Sun Nov 30, 2008 9:29 pm**

s@int wrote:Leon, try typing ipconfig /all in a COMMAND PROMPT WINDOW. See if the Autoconfiguration IP address is a "169.254"( should look something like this - Autoconfiguration IP Address. . . : 169.254.94.38 )
if it is then try this :-

The "Limited or No Connectivity" indication is because the network adapter has failed to get its IP address by DHCP from the router and Windows has defaulted to allocating a "169.254" IP address.

Try repairing the TCP/IP stack and Winsock. Open a Command Prompt window ("Start > Run", type cmd and click OK).

To repair the TCP/IP stack, at the prompt, type...

netsh int ip reset resetlog.txt

...and press Enter

(note the spaces in the command line). The original prompt will reappear.

To reset Winsock entries, at the prompt, type...

netsh winsock reset catalog

...and press Enter

Exit the Command Prompt window and reboot the PC.

did that - no joy.

Posted: **Sun Nov 30, 2008 9:42 pm**

Sabre wrote:
Leonmc0708 wrote:I just clicked "Repair this problem" and it says:

Windows could not finish repairing the problem because the following action could not be completed:
Renewing your IP address

For assistance contact the person who manages your network.

Well, that's us.

COuld you make an ipconfig /all and paste everything it throws back?

Here it is:

Windows IP Configuration

Host Name . . . . . . . : Lynsey
Primary Dns Suffix . . :
Node Type . . . . . . . : Unknown
IP Routing Enabled . . : No
WINS Proxy Enabled . : No

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . . . : Realtek RTL8102E Family PCI-E Fast Ethernet NIC
Physical Address . . . . . . . . . . : 00-21-70-C0-C8-F8

Ethernet adapter Wireless Network Connection:

Connection specified DNS Suffix :
Description . . . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address . . . . . . . . . : 00-23-08-1F-5F-68
Dhcp enabled . . . . . . . . . . . : Yes
Autoconfiguration enabled . . . : Yes
Autoconfiguration IP Address . : 169.254.216.175
Subnet Mask . . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . .:

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . . : MEdia Disconnected
Description . . . . . . . . . . . . . : Dell Wireless 5530 HSPA Mobile Broadband Minicard Network Adapter
Phyical Address . . . . . . . . . . : 02-80-37-EC-02-00

Posted: **Sun Nov 30, 2008 9:47 pm**

Ethernet adapter Wireless Network Connection:

Connection specified DNS Suffix :
Description . . . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address . . . . . . . . . : 00-23-08-1F-5F-68
Dhcp enabled . . . . . . . . . . . : Yes
Autoconfiguration enabled . . . : Yes
Autoconfiguration IP Address . : 169.254.216.175
Subnet Mask . . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . .:

Nice one, that's the relevant part.

Then you didn't get back a "no media", just a bad ip address, I'll come back later, have to check a couple of things.

Posted: **Sun Nov 30, 2008 9:47 pm**

NANNY RED wrote:Leon i had the same problem a few weeks ago my internet provider was Aol an theyd been bought out by carphone warehouse an the ip address i was using wasnt recognised with them as mine was Buffalo . I phoned a lad an he gave me some numbers to type in an when it came up go to a thing called WAN. i got my new username and password from AOL and typed it in an applied it an it was sound. Just phone your internet provider an theyll tell you why its not being recognised,

Sounds a bit like "cheating " to me Nanny

Probably your best bet though Leon.

download and run this Leon

Posted: **Sun Nov 30, 2008 9:59 pm**

Leon mate, we're advancing. Trust me, walk on, at the end of the storm there's a golden sky, and all that.

Well, good news is that your network card doesn't seem to be fúcked. When you get 169.xxx.xxx.xxx, that's something Windows gives you when he can't contact the DHCP server, that is your router.

It may be several factors, now it's a matter of testing.

One candidate might be that your brand new netword card is trying to use too much speed, more than the router can provide, to put it simply. In the device manager, go to the broadband card, right click on it, and go to the advanced tab.

There should be a speed option or something, and it may be in "auto". Just select a standard speed, such as the 100 Half duplex.

I have to have dinner now, I'll come back later, but have faith

Posted: **Sun Nov 30, 2008 10:30 pm**

Sabre wrote:Leon mate, we're advancing. Trust me, walk on, at the end of the storm there's a golden sky, and all that.

Well, good news is that your network card doesn't seem to be fúcked. When you get 169.xxx.xxx.xxx, that's something Windows gives you when he can't contact the DHCP server, that is your router.

It may be several factors, now it's a matter of testing.

One candidate might be that your brand new netword card is trying to use too much speed, more than the router can provide, to put it simply. In the device manager, go to the broadband card, right click on it, and go to the advanced tab.

There should be a speed option or something, and it may be in "auto". Just select a standard speed, such as the 100 Half duplex.

I have to have dinner now, I'll come back later, but have faith

there is no option for speed, but there is one for rate.

Posted: **Sun Nov 30, 2008 10:39 pm**

Posted: **Sun Nov 30, 2008 10:44 pm**

Baz has fixed it

Nice one

Posted: **Sun Nov 30, 2008 10:51 pm**

Dundalk wrote:Baz has fixed it

Nice one

Missus Leon will be delighted on Xmas day!

Posted: **Sun Nov 30, 2008 11:26 pm**

Method one:

Ok, just as you made a ipconfig /all in the new computer and pasted me back, do the same in a computer that does have internet access in your network.

If it's a problem of the DHCP, by setting manually the ip and the gateway of the running computer we could overrule definitely the possibility of network card failure.

If manually setting the ip you get an ip conflict (an error) it's good news, we know the network card is not :censored:

, and then you simply can assign another valid ip, for instance, if the correct one ends in .128, you can assign .130

To manually set these things, go to the network connections, right click on the wireless one, and then go to the properties of tcp ip. Everything should be automatic, you just have to type the ip and gateway that the ipconfig /all of your other computer gives.

Even if this will leave temporarily the correct computer without connection, we'll advance a lot and the problem will be solved by simple changing the ip again.

Method two:

If you don't like method one, I need more info

run in the cmd the network diagnostics:

ntsh diag gui

This will open a window, and at the end, open the tree of your wireless adapter and paste me everything you find, something like this example of my computer:

Caption = [00000001] NIC Fast Ethernet PCI Familia RTL8139 de Realtek
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 192.168.1.1(Misma subred) (Efectuado)
Haciendo ping a 192.168.1.1 con 32 bytes de datos:
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Estadísticas de ping para192.168.1.1:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdida)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, máximo = 0ms, promedio= 0ms
DefaultTTL = 64
Description = NIC Fast Ethernet PCI Familia RTL8139 de Realtek - Minipuerto del administrador de paquetes
DHCPEnabled = Verdadero
DHCPLeaseExpires = 22:16:55 28/11/2008
DHCPLeaseObtained = 22:16:55 25/11/2008
DHCPServer = 192.168.1.1 (Efectuado)
Haciendo ping a 192.168.1.1 con 32 bytes de datos:
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.1: bytes=32 hora<1ms TTL=0
Estadísticas de ping para192.168.1.1:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdida)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, máximo = 0ms, promedio= 0ms
DNSEnabledForWINSResolution = Falso
DNSHostName = 38fda5e7b3
DNSServerSearchOrder (Efectuado)
87.216.1.65 (Efectuado)
Haciendo ping a 87.216.1.65 con 32 bytes de datos:
Respuesta de 87.216.1.65: bytes=32 hora=73ms TTL=73
Respuesta de 87.216.1.65: bytes=32 hora=78ms TTL=78
Respuesta de 87.216.1.65: bytes=32 hora=70ms TTL=70
Respuesta de 87.216.1.65: bytes=32 hora=75ms TTL=75
Estadísticas de ping para87.216.1.65:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdida)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 70ms, máximo = 78ms, promedio= 74ms
87.216.1.66 (Efectuado)
Haciendo ping a 87.216.1.66 con 32 bytes de datos:
Respuesta de 87.216.1.66: bytes=32 hora=75ms TTL=75
Respuesta de 87.216.1.66: bytes=32 hora=73ms TTL=73
Respuesta de 87.216.1.66: bytes=32 hora=72ms TTL=72
Respuesta de 87.216.1.66: bytes=32 hora=76ms TTL=76
Estadísticas de ping para87.216.1.66:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdida)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 72ms, máximo = 76ms, promedio= 74ms
DomainDNSRegistrationEnabled = Falso
FullDNSRegistrationEnabled = Verdadero
GatewayCostMetric = 20
Index = 1
IPAddress = 192.168.1.128 (Efectuado)
Haciendo ping a 192.168.1.128 con 32 bytes de datos:
Respuesta de 192.168.1.128: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.128: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.128: bytes=32 hora<1ms TTL=0
Respuesta de 192.168.1.128: bytes=32 hora<1ms TTL=0
Estadísticas de ping para192.168.1.128:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdida)
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, máximo = 0ms, promedio= 0ms
IPConnectionMetric = 20
IPEnabled = Verdadero
IPFilterSecurityEnabled = Falso
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.255.0
IPXEnabled = Falso
MACAddress = 00:15:58:1D:3A:16
PMTUBHDetectEnabled = Falso
PMTUDiscoveryEnabled = Verdadero
ServiceName = RTL8139
SettingID = {A7530600-5247-408B-9E62-5BD262188F11}
TcpipNetbiosOptions = 0
TcpMaxDataRetransmissions = 5
TcpNumConnections = 100
TcpWindowSize = 60352
WINSEnableLMHostsLookup = Verdadero

But it will be in english (True instead of verdadero)

----

Also, another question, when you tried Saint's reset, did you get a success message after typing it?

And, in the speed option you found, was one of the options "100 half duplex"? If so, select it.

Posted: **Sun Nov 30, 2008 11:49 pm**

Missus Leon expresses her sheer unbridled gratitude!
25/12/09
:laugh:

Posted: **Sun Nov 30, 2008 11:55 pm**

and once you've finished sorting out leon, sabre, can you finally help me get my wireless cable connection up like you promised? i know i'm not a mod or anything but that doesn't mean you don't have to help me.

Posted: **Mon Dec 01, 2008 12:00 am**

andy_g wrote:and once you've finished sorting out leon, sabre, can you finally help me get my wireless cable connection up like you promised? i know i'm not a mod or anything but that doesn't mean you don't have to help me.

*sigh*

If you promise me to be as patient as Leon, I will.

And don't complain, Leon never got his chorizo bribe!

Posted: **Mon Dec 01, 2008 12:07 am**

Sabre wrote:And don't complain, Leon never got his chorizo bribe!

it doesn't even bear thinking about what judge and his tribe will make of that line...

Liverpool FC Forum

Sabre or other geek help request