somthing wrong with my comp after the lan

so i got home and set my computer back up, but now it wont connect to the internet, all the other computers in the house will still connect fine but my desktop just tells me limited or no connectivity. Anyone else have or have had this problem? Could really use some help, im lost.

_________________
You sir just got pwned.

a little more info to work off, when i try to repair it says limited or no connectivity and when i tried to ipconfig release/renew it says "an error occurred while renewing interface wireless network connection 3: unable to contact your DHCP server. Request has timed out. not sure what that means exactly. Ive tried unpluging the router, shuting down the computer, just about everything I can think of.

_________________
You sir just got pwned.

And last I get the same message for both lan and wireless. so regardless of how i try and connect i cant. Is it possible that the lan at PDXlan just screwed up my ability to connect because at this point i dont plan on attending anymore if it does stupid stuff like this.

_________________
You sir just got pwned.

just go reset your router, power it all off for 10 second and then power back on, I get this alot and it usually fixes it.

_________________
590sli motherboard
amd x2 5400+ 2.80 ghz
3870

http://www.speedtest.net/result/282933587.png

just tried doing that for the 3rd time, dosent have an effect. Still just tells me limited or no connectivity. Sad

the only thing i can think of is that a system setting was changed to connect to the lan and for some reason that messed everything up. Because it worked just fine when I left and refuses to work now at home even after I have done everything I normaly do to get rid of this problem.

_________________
You sir just got pwned.

I think I remember this happening at a previous PDXLAN. I believe that there was a batch file that you could download that fixes the problem. It was a long time ago so I don't remember what the specific issue was though. Xilace would be the one to ask about this.

_________________
Cheerio, let's do it again.

http://www.download3k.com/Install-WinSockFix.html

try that

Its likely not a win sock issue, its just name resolution and a node types. From your cmd prompt do an IPCONFIG /ALL and 3rd entry should be "Node Type" mine for example is Hybrid, which means I use a WINS server first for my name to IP addy translation first, and then if that doesnt work, a broadcast package. You home network uses you ISP's WINS server, so you run in hybrid mode. At the LAN they likely dont use wins, and just use B-node (broadcasts only) for name resolution. On your home network without WINS, you would not be able to hit web addresses as your router and comcast/qwest or who ever your home isp's router will route your broadcast messages.

Most network cards will pick up the change just fine. Some do not. If yours says unknown or B node or broadcast for node type you can go to Regedit and go to:

HKEY_Local_Machine\System\CurrentControlSet\Services\NetBT\Parameters Click on the DhcpNodeType key and set it to 8. You may need to reboot to see the change.

This is not the fault of the network, just a hardware/software issue detecting the change. The batch file mentioned earlier just makes this change for you.

Jeep's Right - I identified this symptom after staffing PDXLAN 6 and posted a fix, and Notoes automated it for me. You can try copy/paste the following block into a Command Prompt window, or it can go into a text (Notepad) document and saved with a ".bat" extension (e.g. netfix.bat) to make a quick double-clickable script.

Code:

@echo off
echo Registry file by Notoes
REG DELETE HKLM\System\CurrentControlSet\Services\Netbt\Parameters /V DhcpNodeType
REG ADD HKLM\System\CurrentControlSet\Services\Netbt\Parameters /V NodeType /T REG_DWORD /D 1
ipconfig /release
echo IP has been released, press any key to renew
pause
ipconfig /renew
echo IP Should have been renewed, Networking Browsing should be good to go!
end

Sorry about the difficulties; I thought we fixed this after PDXLAN 6.

_________________
Silverstone SG03, Asus P5E-VM, QX9650, 8GB OCZ-Titanium
Sapphire 4890 2GB, 300GB Velociraptor, 1TB Caviar, Samsung DVD/RW

SpoonDogSVT wrote:

Sorry about the difficulties; I thought we fixed this after PDXLAN 6.

this has been resolved many lans ago from when somebody insisted on setting up a wins server on the network. We actually used the EXACT same config, server, and everything else in regards to dhcp, dns, and wins that we used for i believe pdxlan 9, showdown lan san jose (twice i believe), pdxlan 10, and will use for showdown lan indy coming up in a week.

If this were a recurrence of what happened at pdxlan 6 then many more people would be posting with this issue. and not to mention i wouldnt be able to use this computer to type this message at this very moment Wink

Hope all is well and you manage to get it fixed. I'd suggest making a valiant effort with the instructions that spoondog posted.

I ran the .bat file spoon posted and deleted the DhcpNodeType when it asked y/n, it released fine but then i got the same unable to contact your DHCP server. reqest has timed out when I tried to /renew.

_________________
You sir just got pwned.

Are you not getting an IP or just can't navigate to named addresses? I've had that happen before with DHCP and a good #ipconfig /flushdns did the trick. Razz

_________________
www.pdxclan.com

ok new breakthrough, if I go in and turn off WEP the internet works fine on my desktop, but when I go to turn it back on, my desktop goes back to limited connectivity, guess now my questions are, is there a way to fix this, and if you cant think of any how important is it to have WEP turned on?

_________________
You sir just got pwned.

if its your gaming system i'd go hard wired. if its a laptop and you want mobility i would suggest at least using WPA. If your wireless AP can support it and your system can support it, i would suggest WPA2. As well as using a long key such as something like this "I dont use WEP cuz WPA2 is cooler!" spaces, caps, no caps, numbers, symbols, and length help it from being cracked so easily. (WEP takes minutes to crack)

Mind you that if your using XP you will probably need to install this hotfix from microsoft to get WPA2 to show up in your list. http://support.microsoft.com/kb/893357 . Also note that you would want the one that says something like "WPA2-Personal" or "WPA2-PSK" which stands for preshared key.