Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Acquiring IP address forever


  • Please log in to reply
10 replies to this topic

#1 Eyesee

Eyesee

    Bleepin Teck Shop


  • BC Advisor
  • 3,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:05:20 AM

Posted 19 June 2010 - 04:03 PM

System is a Compaq Presario sr2050nx with XP Media Center Edition SP3

Cust reported that the system would not connect to the Internet. Onboard NIC keeps attempting to acquire an IP address forever. Thinking the onblard was bad I disabled it and installed a working used SMC PCI card from spare parts.
I removed a moderate infection with Avast, MalwareBytes, SuperAntispyware and Spybot.
I tested the Internet & everything seemed OK.
They took it home and reported that everything was fine until they turned it off. Then they had the same problem.
Thinking that the card might have gotten toasted with a recent thunderstorm I replaced it with a new Realtek RTL8169. It also cannot acquire an IP address. Tried three new cards. All do the same thing. Tested all in one of my systems. They all work.
When attempting to release & renew the ip address with ipconfig it reports the RPC server is unavailable

I have tried
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /registerdns
winsockxpfix
Dropped the speed down to 10 mbps full duplex
disabled netbios over tcp/ip
It will ping 127.0.0.1

Interesting thing is today it worked with the onboard enabled, until I turned the system off. Then it wont acquire the IP address again.
I am beginning to wonder if the system is still infected

Anybody have any ideas?
In the beginning there was the command line.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:20 AM

Posted 19 June 2010 - 04:23 PM

Google List

I looked at 2 of the first 3 listed...worth reading, IMO.

Louis

#3 Eyesee

Eyesee

    Bleepin Teck Shop

  • Topic Starter

  • BC Advisor
  • 3,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:05:20 AM

Posted 19 June 2010 - 04:43 PM

That is exactly where I have been Louis
Went through almost all of them
In the beginning there was the command line.

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:20 AM

Posted 19 June 2010 - 05:01 PM

Then I would travel the clean install road.

If that fails to solve it...the logical choice, IMO, would be bad motherboard (a road I never travel down, but is always a possibility).

Louis

#5 Eyesee

Eyesee

    Bleepin Teck Shop

  • Topic Starter

  • BC Advisor
  • 3,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:05:20 AM

Posted 19 June 2010 - 05:48 PM

That would be my preferred way to go as well, but I cant. Its a businesses machine.
No recovery cd & I dont have a media center edition cd

I plugged it in a while ago and it connected immediately. Until I turned it off. Then it wont acquire an IP address.

Im thinking that something is still lurking out here messing with the connection but i dont know what else to try.
Mbam Sas and Spybot all say everything is fine
In the beginning there was the command line.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:20 AM

Posted 19 June 2010 - 06:04 PM

Malware...or computer settings...don't work part-time.

You say that you connected previously with no problem...I think that rules out software, O/S, and malware.

I could be wrong :thumbsup:.

As for those users with undue optimism that their systems will never require a reinstall of the O/S...ever...well, I'm just sorry that they don't believe in backups and such.

But they probably don't believe in auto, health, or life insurance...either :flowers:.

The value of these things is proven every day, somewhere in the world.

Louis

#7 prashantrana

prashantrana

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:03:50 PM

Posted 20 June 2010 - 06:26 AM

Automatic ip address works when a DHCP server is installed, you should setup an ip address manually.

Go to start>control panel>network connections

you will then see the available adapters there. right click the one you wish to use and then click on properties. In general select Internet Protocol (TCP/IP) and thyen click on properties. set ip address as 192.168.1.10 (if you are using a router) otherwise 192.168.0.1 subnet remains 255.255.255.0 and default gateway 192.168.1.1 or 192.168.0.1 you can setup DNS or leave it blank. Press ok ok. You should now have a working connection.

If your computer is the one which connects to the internet (non router based) you should use the ip address as 192.168.0.1 and leave the default gateway blank.

Edited by prashantrana, 20 June 2010 - 06:28 AM.


#8 Eyesee

Eyesee

    Bleepin Teck Shop

  • Topic Starter

  • BC Advisor
  • 3,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:05:20 AM

Posted 20 June 2010 - 01:12 PM

Thanks Prashantrana, I was thinking about doing just that actually
Will give it a try tomorrow
In the beginning there was the command line.

#9 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:20 AM

Posted 22 June 2010 - 07:42 AM

I would try replacing the Network Interface Card, they are usually less then 40 bucks. The reason I say this is the fact that it works until your reboot the machine, which means that something is amiss at the hardware level.

#10 jhsmurray

jhsmurray

  • Members
  • 383 posts
  • OFFLINE
  •  
  • Location:6,378 km above the Earth's core
  • Local time:06:20 AM

Posted 22 June 2010 - 10:50 AM

Apart from assigning a fixed IP, is the DCHP Client Service running when the issue arises? What if you restart it?

Acer Aspire 5732z
OS: Windows 7 Ultimate
Processor: Intel Pentium III Xeon, 2200 MHz
RAM: 3 GB
Display: Mobile Intel GMA 4500M

#11 Eyesee

Eyesee

    Bleepin Teck Shop

  • Topic Starter

  • BC Advisor
  • 3,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:05:20 AM

Posted 22 June 2010 - 05:06 PM

I opted for a clean install
Problem solved. Even with the onboard NIC
Go figure huh?

Thanks All!
In the beginning there was the command line.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users