An exclusive gaming industry community targeted
to, and designed for Professionals, Businesses
and Students in the sectors and industries
of Gaming, New Media and the Web, all closely
related with it's Business and Industry.
A Rich content driven service including articles,
contributed discussion, news, reviews, networking, downloads,
and debate.
We strive to cater for cultural influencers,
technology decision makers, early adopters and business leaders in the gaming industry.
A medium to share your or contribute your ideas,
experiences, questions and point of view or network
with other colleagues here at iVirtua Community.
I have a problem. I have to manually put my IP addy in (192.168.0.1) for example. I can't get my XP Home/SP2 to auto select the correct IP. I have two identical systems, puchased at the same time. The one I use has the problem, the other one will renew and assign fine.
I also have a problem with my net (dialup) :( connection 'freezing'.. it does not actually disconnect, it just dies, no data passed; I wonder if it is some how related, perhaps winsock issue or what?
I have a problem. I have to manually put my IP addy in (192.168.0.1) for example. I can't get my XP Home/SP2 to auto select the correct IP. I have two identical systems, puchased at the same time. The one I use has the problem, the other one will renew and assign fine.
I also have a problem with my net (dialup) :( connection 'freezing'.. it does not actually disconnect, it just dies, no data passed; I wonder if it is some how related, perhaps winsock issue or what?
Thanks!
Doesn?t Windows XP assign different IP addresses & keeps the correct one hidden for security purposes?
Go to your LAN settings in \"Internet Options\" and make sure UN Check the \"Automatically Detect Settings\" & also make sure your Dial Up is default.
I do think it's a winsock issue. You're probably getting a 169 addy when you try to ipconfig /renew.
I'd suggest downloading the free tool called Winsockfix.exe and run it. See if it fixes your problem...if it does not, I really don't have many other ideas for you other than suggesting a reload.
Just out of curiousity--did you happen to get hammered with spyware on that computer?
it is a 169 addy, these computers are about 3 weeks old, I reloaded from HPs recovery but still have the issue. I'm not overclocking; I'll try the winsockfix
Digg Topic
Tag topic on On del.icio.us
Technorati Search
Post to Slashdot
