Win XP Pro is busting my balls
 

I just put together a new pc, and I bought/installed Win XP Pro on it. Everything went just fine until I hooked up the new pc to my router (cable modem hooked up to a router - already had 3 pc's working just fine). For some reason, this new pc will not update the dynamic IP. It does not recieve packets, only seems to try to send packets.

The ASUS mother board came with a network connection built in - that didn't work. I disabled it in BIOS, installed a D-Link fast ethernet card - same problem - does not recieve packets, unable to renew the IP address.

I also tried pluuging the R5 cable from the new pc dirertly into the cable modem - no dice. No Internet.

I have checked the IE connection and the network connection to make sure they told to check IP/DNS dynamically - but they dont seem to be able to do it. I have hit Microsoft support chat(they gave me http://www.practicallynetworked.com/ URL - good info, still no results), and I have a thread going on MS support groups - which might work out, but so far, I am just repeating info given in the first post. I checked my ISP website (RoadRunner) and they gave TCP/IP info which matches what I have it set up as. They also mention a prolem with XP and USB port problems on the Motorola cable modem, but that doesn't apply to me, as the modem is hoked up to a router, not a USB port.

So, I figure the best and fastest place to look for info is GFY. What can I try?

If I had a nickle for everytime OS X did that to me I would be a really poor man. I don't know what to tell you man, I've heard of others having similar problems.

I will bust your balls baby!

well, if it doesn't get solved her, but elsewhere, I'll post the remedy.

Get in line. Busting my balls is a national pastime. They show highlights on ESPN.

Go to the network properties for the NIC and remove and re-install tcp/ip then reboot. (It may or may not ask)

Sounds like the tcp/ip driver got hosed somehow.

I have had that problem many times in the past also.

I currently run Win 2000 pro on my networked machines, with NTFS.

I haven't had any problems doing it this way.

AST 121760557

The problem with Win XP is that it tries to be like Mac. It's all stupid looking and tries to really dumb things down, just like mac. Unfortunately they just fucked up a good thing.


Uh, hello. .
Win Xp (Dumb)
os X (and Dumber)



Go back to 2000 pro and be done with it. Or just buy a mac.

use linux it's much better and more confusing all at the same time :thumbsup

Make sure you have the following protocol installed:

NWlink NetBios
NWlink IPX/Netbios Compatible Transport Protocol
and naturally:

Internet Protocol ( TCP/IP)

I would think the first step would be to take a laptop (if oyu have one) and plug the same cable your plugging into your computer into the laptop and see if the laptop gets an ip.

I'm stunned at how your post goes from really stupid to brilliant.

busting balls eh?

is that kinda like the trample fetish?

I swapped R5 cables with another machine - new cable worked fine on the older pc. Old cable on new pc had same problem.

will try this right now

Thanks. Anyone stupid enough to put XP on a machine deserves a mac. That's just about all this loser is good for. Mac is made for total fuckin' morons.

I see it like this. There are more PC related problems because there are more PC users. I once read a stat (probably outdated now) but it said that mac made up only 4 % of the internet population. I bet that if you increased Mac users to 50%. Assuming that only mac and PC (not including different OS's, just 50% pc, and 50% mac,) are being used, that you'd have a very equal balance of complaints against both systems.

Bottom line is it all comes down to preference. I was on a mac for years. I tried a pc, and became familiar with it. It's a thinking mans computer. I was able to go in and tweak shit that I couldn't with my mac. I could fix things. I liked that. I can build my own from scratch just exactly how I want it.

I one time had to call out a technician to replace a battery for my clock on a mac, (this was years ago).

I'm sure mac's have come along way since then, but since I switched, I'll never go back. My Pc is like my 68 camaro. I can go in and add enhancements, make adjustments, tweak it, rev it up and go.

That said, I can also state that pc's aren't for everyone. I like mine because I know it in and out. Most people want to just turn it on and be totally satisfied with what they are stuck with, in that case, by a mac.

I'm a fuckin' man, I like to build shit, and I like to fix shit, I like to tweak shit.

And didipimp..
If I ever see you,
I'm going to CTRL+ALT+DELETE you!

When all else fails, quote Weird Al.

dude, what the hell? that's fucked up. you're a little extreme... but ok.




anyways, steve i've had this problem before. it seems that windows xp has trouble with this sometimes, especially when connected to like a cable modem or soemthing, and not a true router.


2 things to do. even though you're using dhcp, i suggest you put the DNS ips in the network config, it works a lot more stable.

and, to fix your networking issues, this is probably what you need to do. i used to do it all the time. you just go to your network setting and disable then re-enable your network connection. it wil fix it that way.

easier way to do this is just go start->run->cmd

then type:

ipconfig /release

ipconfig /renew


all fixed! :)

The ISP uses dynamic IPs. I wouldn't mind trying to load in the IPs manually just to see if it would work, though. Where can I do this? I didn't see this in the Tools->Connections->Properties etc or in Network connections either. I figure I can try pluggin in the IP info off one of the other machines and see if it will work this way.

I just tried this again - still no luck. I have actually gone back and forth between the on mobo network connection and a D-Link card. Same shit so far.

it just hangs when I try to run /renew - it times out, and does not grab the IP info off the router.

XP Pro is upposed to be the most stable and up to date version of Windows available right now. I have been using Win 2000 for a while on my own pc, and liked that - but honestly, if this new pc wasn't having this problem, I could give two shits which version I am using.

Looks like you like to say "shit", too. I'm not looking to compare testosterone levels or sperm count with you, I just want this new pc to work with the router.

It's just part of being a husband/dad. :winkwink:

Ok guess that didn't work.

Make sure the box below is checked...



if that's not it. go step by step over the TCP/IP properties and compare them with a PC that works

One wrong check and it's all over...

http://www.rndinternet.com/ip.jpg

Hey Steve, I just thought of something else. Try

ping localhost

and see if you get a reply.

Install service pack 1 if you have not done so.

Solved a lot of issues for me.

if everything is setup correctly with your pc, my guess is something is messed up with the router or something. it should work, i use a netgear router on my setup (i don't need to, but i do it anyways). i didn't see, did you try resetting the router?

and with the DNS, i mean allow the machine to get a dynamic ip, but tell it what DNS it's using. there are 2 parts in the ip setup in network connections, one says "obtain ip address automatically", this is ok, and then below it says "obtain DNS information dynamically". switch this over to the "use this DNS information" or whatever and manually enter your dns.

This is exactly how mine is looking right now. I think I got gremlins in this puppy.

Do you have ICQ?

OK, this gave me the same info on both the pc I am typing from (works fine) and the new ballbuster. So it is pinging localhost the same as a working pc.

:thumbsup

thats what fixed mine!

the only thing i'm running right now is QoS packet scheduler and tcp/ip. works here :)

Thanks, but I did install this.

I'll give this a try and see if it works for me, too.

you really shouldn't need anything else, even if you're sharing files on your subnet. win xp does netbios over tcp/ip, and got rid of netbeui. this does make a sort of troublesome issue networking non-xp machines and xp machines for file sharing through netbios, but it works great for xp machines.

It is a very common problem I have, based on what you have said.

The built in port more than likely works.

It is a problem I have with road runner, now called cox cable in my area. If you want to call me, I am fairly sure I can help you with this.......
Aron
Email me for my number
[email protected]

Start -> Run -> cmd

then

ipconfig

what does it say?

hell yeah, that's when i had this issue with my system, it was always freaking cable. then it had a little issues on my ppoe dsl... but when i switched over to ppoa with a real router attached, the problem went away. i think it also went away when i had bus. cable line... but that also had a real router and not a modem.

Stupid question, but have you tried plugging in to a different port on your router? And by chance are you plugged into the uplink port?

We now have Bus Cable, and have 10 ip's so that helps
with the problems, but if I hook a new computer up, to the HUB, the entire system has to be reset, for 5-15 minutes.
Then the computer turned on, then the whole ipconfig deal
Then refresh on a browser a couple of times, get those packets moving, LOL

yeah, cable is very picky with MAC addresses, especially the res. type modems. the cisco ubr900 isn't that way... but again it's a router (i beleive now they use xyzel or some crazy thing). if a machine is changed and the mac address isn't correct, modems generally wig out. at least the toshiba ones do.

yeah, make sure you've got a good link, maybe try another cable.

I almost wonder if the cable company won't let you have another IP address until the lease on one of your current IPs expires.