|
From: compgirl on 20 May 2008 23:35 hello, i am new to this, but after posting on several others and searching endlessly for information online and other forums such as this, i have found no post/thread specific to my situation, so i am going to start a new thread. i would really appreciate any help you can provide!:) our home has a cable connection and two computers, a laptop that connects wirelessly using an 802.11g 4-port router, and a desktop with a wired connection. the laptop never has had any problems; it will connect directly through the cable modem, wired and wirelessly through the router. the desktop has been having issues forever...it would randomly connect to the network, work for weeks at a time, but then stop. it would always work connected to the cable modem. after trying just about everything i (and everyone i know and spoke with) could think of, i reformatted the desktop (there were other problems too...). while drastic, everyone agreed that i had tried everything. i did not have the recovery disk, so after reformatting with xp sp2; i went online with the laptop and got the necessary drivers and utilities (mostly from the dell site) on a flash drive. i installed everything and set the tcp/ip settings in the properties of the local area connection (which always has limited or no connectivity), but i still cannot get online with that computer. (i can still get online with a direct connection to the cable modem.) after trying many, many things, someone suggested that i check the 'enable proxy' parameter in the registry, which was when i noticed that it didn't exist. (not that i can see...can that be hidden???) neither do most parameters associated with dhcp. this makes sense why i cannot get an ip from the router, but i can find very little info (and i have stumped many of my friends) on what to do if the values of them are incorrect. i cannot even log into the router from the computer (nor can i see the computer on the network from the laptop). there is no weird software (beyond some weird broadcom suite i installed by mistake but i have checked...it's on my laptop and causing no problems). i have a degree in computer science, so i am not a novice...although i did leave a lot out of this message (had i included everything i have done this would be the worlds longest post...4 months now). i also have been working out of the field for awhile (3 years), and when i did was in software design...most of my networking skills are a bit dated (but i have always known at very least enough to have all my computers at home online with no problems). if you could, imagine i have tried all the basics...if you have something new or different i can try, please help...until i fix the desktop i am <i>sharing</i> my laptop! his desktop used to be used at his office so i do not have the exact specs on it...it's a dell optiplex gx280 (there is some info on dell's site) - basics; p4 2.8GHz, 512 MB RAM, 80 GB maxtor HD...nothing specific. (but there are some things i have discovered in all of this, so please ask anything that may clarify!) that also means it was on XP Server network, but the reformat would have taken care of those settings, right? thank you, jennifer sorry i can't post the ipconfig /all, but i cannot get online using the computer with the problem! (it looks NOTHING like my laptop's...including the auto appended dns suffix):mad:
From: compgirl on 20 May 2008 23:37 oh - while it has come up again fixing this - what is the node type in xp...i've always wondered but it never seemed to matter.
From: Steve Winograd on 21 May 2008 12:39 On Tue, 20 May 2008 22:37:51 -0500, compgirl <compgirl.39rnqx(a)no.email.invalid> wrote: >oh - while it has come up again fixing this - what is the node type in >xp...i've always wondered but it never seemed to matter. The node type determines how Windows XP uses NetBIOS broadcasts and/or WINS server queries to resolve computer names to IP addresses. For details: Default Node Type for Microsoft Clients http://support.microsoft.com/default.aspx?scid=kb;en-us;160177 TCP/IP and NBT Configuration Parameters for Windows XP http://support.microsoft.com/default.aspx?scid=kb;en-us;314053 A computer in a workgroup network should use a value of 1 (B-node) or 4 (M-node). Specifying the wrong value can cause name resolution to fail. For example: 1. A value of 1 (B-node) on a routed network with multiple subnets. NetBIOS broadcasts don't cross routers. 2. A value of 2 (P-node) on a computer in a workgroup network. A workgroup network doesn't have a WINS server. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional Program http://mvp.support.microsoft.com
From: compgirl on 21 May 2008 22:39 thank you for the wonderful explanation about node types. i have always been curious, and although it was never a problem in the past thank you. seeing the answer makde me realize that not understanding the basics could lead to problems. does anyone have any input about my other problem? on a very simple level - what conditions could cause the registry parameters to be missing? (example - "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\Enable Proxy", there is a listing under parameters, just certain varibles are missing) thanks so much!
From: Steve Winograd on 23 May 2008 13:10 On Wed, 21 May 2008 21:39:15 -0500, compgirl <compgirl.39snh2(a)no.email.invalid> wrote: >>>oh - while it has come up again fixing this - what is the node type in >>>xp...i've always wondered but it never seemed to matter. >> >>The node type determines how Windows XP uses NetBIOS broadcasts and/or >>WINS server queries to resolve computer names to IP addresses. For >>details: >> >>Default Node Type for Microsoft Clients >>http://support.microsoft.com/default.aspx?scid=kb;en-us;160177 >> >>TCP/IP and NBT Configuration Parameters for Windows XP >>http://support.microsoft.com/default.aspx?scid=kb;en-us;314053 >> >>A computer in a workgroup network should use a value of 1 (B-node) or >>4 (M-node). >> >>Specifying the wrong value can cause name resolution to fail. For >>example: >> >>1. A value of 1 (B-node) on a routed network with multiple subnets. >>NetBIOS broadcasts don't cross routers. >> >>2. A value of 2 (P-node) on a computer in a workgroup network. A >>workgroup network doesn't have a WINS server. > >thank you for the wonderful explanation about node types. i have always >been curious, and although it was never a problem in the past thank you. >seeing the answer makde me realize that not understanding the basics >could lead to problems. > >does anyone have any input about my other problem? on a very simple >level - what conditions could cause the registry parameters to be >missing? (example - >"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\Enable >Proxy", there is a listing under parameters, just certain varibles are >missing) > >thanks so much! You're welcome! I'm sorry, but I don't know the answer to your other problem. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional Program http://mvp.support.microsoft.com
|
Next
|
Last
Pages: 1 2 Prev: Guest vs Owner details Next: Windows AD accounts randomly locking on 1st attempt |