Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

"Limited or no connectivity" error; PLEASE HELP!

Started by crazycoolmarc14 , Apr 25 2008 02:33 PM

  • Please log in to reply

#1
crazycoolmarc14
Posted 25 April 2008 - 02:33 PM

crazycoolmarc14

    New Member

  • Member
  • Pip
  • 5 posts
Okay, I'm running Windows XP SP2. I've connected my ethernet cord from my PC to a free port in my router. My router is a Belkin54g and so far I have had no troubles with it. I know that it's nothing wrong with the router, as I have even directly connected my computer to the internet. What's wrong? I've renewed and released using ipconfig but nothing works! It comes up with an error stating that it cannot connect to the DHCP server... So I'm thinking that it's something wrong w/the computer. Any fixes? Much appreciated!
  • 0

Advertisements

#2
Artellos
Posted 25 April 2008 - 03:44 PM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts
Lets renew your connection to the gateway.
  • Go to Start -> Run.
  • In the Box, type in "cmd".
  • A black box will appear. Type in: "ipconfig /release".
  • After it is done releasing. Type in: "ipconfig /renew".
  • This should renew your connection with your gateway.

I know you tried it. Make sure you follow THIS order! First the release, then the renew.
You can also Try fushing the DNS.

  • Go to Start -> Run.
  • In the Box, type in "cmd".
  • A black box will appear. Type in: "ipconfig /flushdns".
  • This should clean your DNS cache.


Regards,
Olrik
  • 0

#3
Ztruker
Posted 25 April 2008 - 04:38 PM

Ztruker

    Member 5k

  • Technician
  • 7,091 posts
If that doesn't work, please post the output from ipconfig /all run from a command prompt.

On my computer it looks like this (using code box to maintain formatting)
Windows IP Configuration

		Host Name . . . . . . . . . . . . : desktop
		Primary Dns Suffix  . . . . . . . :
		Node Type . . . . . . . . . . . . : Unknown
		IP Routing Enabled. . . . . . . . : No
		WINS Proxy Enabled. . . . . . . . : No
		DNS Suffix Search List. . . . . . : router

Ethernet adapter Local Area Connection:

		Connection-specific DNS Suffix  . : router
		Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connectio
		Physical Address. . . . . . . . . : 00-E0-18-4F-1D-57
		Dhcp Enabled. . . . . . . . . . . : Yes
		Autoconfiguration Enabled . . . . : Yes
		IP Address. . . . . . . . . . . . : 192.168.2.11
		Subnet Mask . . . . . . . . . . . : 255.255.255.0
		Default Gateway . . . . . . . . . : 192.168.2.1
		DHCP Server . . . . . . . . . . . : 192.168.2.1
		DNS Servers . . . . . . . . . . . : 192.168.2.1
		Lease Obtained. . . . . . . . . . : Friday, April 25, 2008 5:38:38 PM
		Lease Expires . . . . . . . . . . : Saturday, April 26, 2008 5:38:38 PM
This is on a HP 750c connected to a Dell Wireless 4 port router via Ethernet cable.
  • 0

#4
crazycoolmarc14
Posted 26 April 2008 - 01:53 AM

crazycoolmarc14

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
Okay, sorry I'm late. I did an ipconfig/all and it came up with this:

"Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix:
Description: Intel<R> Pro/100 VE Network Connection
Physical Address: 00-0C-6E-61-7F-CA
Dhcp Enabled: Yes
Autoconfiguration Enabled: Yes
Autoconfiguration IP Address: 169.254.12.0
Subnet Mask: 255.255.0.0
Default Gateway:"

I know that it's AutoConfig IP Address being a 169 number is the problem. I continue to reset the router, still, nothing. Thanks for input, once again!

Edited by crazycoolmarc14, 26 April 2008 - 02:00 AM.

  • 0

#5
Artellos
Posted 26 April 2008 - 02:56 AM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts
Just for clarifications sake :)
I'd like to see some more information. Please follow the steps below.
  • Go to Start -> Run.
  • In the Box, type in "cmd".
  • A black box will appear. Type in: "ipconfig /all".
  • A lot of information will appear, Please right click the black window and hit mark.
  • Select every line of text you recieved and copy it into your next reply.

Note the bolded lines.

Regards,
Olrik
  • 0

#6
The Skeptic
Posted 26 April 2008 - 12:09 PM

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
You say that you connected the computer "directly to the internet" so I understand that the computer was connected to a modem, the router didn't play any part and you still had the problem. If I am correct then please do the following:

1: Leave the router out and connect directly to the modem. If you are not sure how to create a new internet connection please let us know.

2: When connected run ipconfig /all and write down the DNS servers

3: In the same cmd screen type ping dns IP and press Enter.

4: If failed or if reply time is very long open control panel > network connections. Double click the connection that you created and under Support click Repair. Windows will try to repair the failed connection by flushing ip.

5: If there is still no connection use this link and click Reset TCP/IP. If still no connection go to the same site and click Repair Winsock. Read the instructions first.

6: If still no good go to Device Manager, expand Network Adapters, right click the adapter and choose to uninstall the driver. Reboot the computer and let XP reinstall the driver automatically.

7: If still no good then there is a possibility that the Ethernet card in your computer is faulty and needs replacement. If the card is integrated with the motherboard then you will have to get a pci ethernet card and install it in a free slot.
  • 0

#7
Ztruker
Posted 26 April 2008 - 01:51 PM

Ztruker

    Member 5k

  • Technician
  • 7,091 posts
3: In the same cmd screen type ping dns IP and press Enter. ???

I think you meant ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the DNS IP address, right?

I thought perhaps there was a special ping action taken if you entered ping dns xxx.xxx.xxx.xxx but it just returns invalid. I know I took it literally but perhaps crazycoolmarc14 would also?
  • 0

#8
The Skeptic
Posted 26 April 2008 - 02:00 PM

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
Quote: "I think you meant ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the DNS IP address, right? "

That's correct. The way you write it down is clearer then mine. Thanks.
  • 0

#9
crazycoolmarc14
Posted 27 April 2008 - 06:41 PM

crazycoolmarc14

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
Okay, did a "ipconfig/all" and it came up with this:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Marc>ipconfig/all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-0C-6E-61-7F-CA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.12.0
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

C:\Documents and Settings\Marc>
  • 0

#10
crazycoolmarc14
Posted 27 April 2008 - 08:02 PM

crazycoolmarc14

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
This may be of some importance; I just checked the security log on my router (Belkin54g) and it came up with a bunch of "Smurfs"... What's that? Here it is:

"04/25/2008 14:14:41 sending OFFER to 192.168.2.2
04/25/2008 14:14:17 sending OFFER to 192.168.2.2
04/25/2008 14:14:12 sending OFFER to 192.168.2.2
04/25/2008 14:10:01 192.168.2.3 login success
04/25/2008 14:08:23 sending OFFER to 192.168.2.2
04/25/2008 14:08:15 sending OFFER to 192.168.2.2
04/25/2008 14:08:10 sending OFFER to 192.168.2.2
04/25/2008 14:06:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 14:06:16 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 14:06:12 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 14:06:09 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 14:06:07 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 14:02:42 sending OFFER to 192.168.2.2
04/25/2008 14:02:25 sending ACK to 192.168.2.3
04/25/2008 14:02:19 sending OFFER to 192.168.2.2
04/25/2008 14:02:16 sending OFFER to 192.168.2.2
04/25/2008 14:02:04 sending OFFER to 192.168.2.2
04/25/2008 14:01:47 sending OFFER to 192.168.2.2
04/25/2008 14:00:02 sending ACK to 192.168.2.3
04/25/2008 13:58:10 sending ACK to 192.168.2.3
04/25/2008 13:58:09 sending OFFER to 192.168.2.3
04/25/2008 13:56:06 sending OFFER to 192.168.2.2
04/25/2008 13:54:00 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:53:56 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:53:52 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:53:48 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:51:34 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:51:30 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:51:28 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:49:40 sending OFFER to 192.168.2.2
04/25/2008 13:49:24 sending OFFER to 192.168.2.2
04/25/2008 13:49:16 sending OFFER to 192.168.2.2
04/25/2008 13:49:13 sending OFFER to 192.168.2.2
04/25/2008 13:43:24 sending OFFER to 192.168.2.2
04/25/2008 13:43:16 sending OFFER to 192.168.2.2
04/25/2008 13:41:42 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:41:36 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:41:32 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:41:29 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:41:28 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:37:55 sending OFFER to 192.168.2.2
04/25/2008 13:34:51 sending ACK to 192.168.2.3
04/25/2008 13:33:42 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:40 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:37 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:32 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:30 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:28 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:25 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:33:18 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:31:12 sending OFFER to 192.168.2.2
04/25/2008 13:29:23 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:29:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:29:17 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:29:14 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:29:13 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:29:08 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:25:16 sending OFFER to 192.168.2.2
04/25/2008 13:25:13 sending OFFER to 192.168.2.2
04/25/2008 13:21:29 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:19:18 sending OFFER to 192.168.2.2
04/25/2008 13:19:14 sending OFFER to 192.168.2.2
04/25/2008 13:17:03 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:17:01 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:16:59 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:16:57 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:16:50 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:16:49 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:12:48 sending OFFER to 192.168.2.2
04/25/2008 13:10:18 sending ACK to 192.168.2.3
04/25/2008 13:06:47 sending OFFER to 192.168.2.2
04/25/2008 13:06:24 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:06:22 sending OFFER to 192.168.2.2
04/25/2008 13:06:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:06:18 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:06:17 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 13:05:41 sending OFFER to 192.168.2.2
04/25/2008 13:05:16 sending OFFER to 192.168.2.2
04/25/2008 13:05:11 sending OFFER to 192.168.2.2
04/25/2008 12:56:43 sending OFFER to 192.168.2.2
04/25/2008 12:56:27 sending OFFER to 192.168.2.2
04/25/2008 12:56:13 sending OFFER to 192.168.2.2
04/25/2008 12:55:12 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:55:10 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:27 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:24 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:22 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:19 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:18 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:16 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:14 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:12 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:07 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:05 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:04 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:53:01 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:58 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:57 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:55 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:53 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:52 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:49 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:48 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:46 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:41 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:40 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:38 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:37 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:35 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:34 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:33 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:31 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:30 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:27 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:25 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:23 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:18 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:16 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:14 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:13 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:10 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:08 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:07 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:05 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:52:01 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:58 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:56 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:55 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:52 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:51 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:49 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:48 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:45 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:43 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:42 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:39 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:37 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:36 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:34 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:33 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:31 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:30 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:28 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:26 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:51:25 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:41 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:39 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:21 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:19 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:18 sending OFFER to 192.168.2.2
04/25/2008 12:50:17 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:50:16 **Smurf** 169.254.255.255->> 169.254.12.0, Type:3, Code:3 (from WAN Outbound)
04/25/2008 12:49:41 sending OFFER to 192.168.2.2
04/25/2008 12:49:18 sending OFFER to 192.168.2.2
04/25/2008 12:46:40 DHCP Client: Receive Ack from 192.168.1.1, 'Lease time'=72000
04/25/2008 12:46:40 DHCP Client: Send Request, Request IP=192.168.1.4
04/25/2008 12:46:40 DHCP Client: Receive Offer from 192.168.1.1
04/25/2008 12:46:40 DHCP Client: Send Discover
"
  • 0

#11
TheQuickBrownFox
Posted 27 April 2008 - 11:20 PM

TheQuickBrownFox

    Member

  • Member
  • PipPipPip
  • 714 posts
To the experts:
I'm just guessing, but does the log say there's a DoS?
  • 0

#12
The Skeptic
Posted 27 April 2008 - 11:31 PM

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
We suggested a whole list of procedures, following each other in a logical order. Have you tried them?
  • 0

#13
deetce
Posted 19 September 2008 - 04:42 PM

deetce

    New Member

  • Member
  • Pip
  • 4 posts
i had the same issue and tried all the ipconfig options which didn't work. somebody then made the suggestion to try the following

start - run - cmd

netsh winsock reset catalog

i have been trying to fix my problem on and off for the last few months and had replaced my hardware twice. after all of that, the one step above seemed to work the best.

good luck
  • 0
Back to Windows XP, 2000, 2003, NT · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Retired Forums
  3. → Windows XP, 2000, 2003, NT

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP