If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
sigh...
some people believe men never landed on the moon.... and that the antivirus companies are the ones writing the viruses... Believe what you want, I prefer to believe fact, not fiction. Carey "Interrogative" wrote in message ... Sorry, you are wrong. It is a well known issue. "Carey Holzman" wrote in message ... Not true. "Interrogative" wrote in message ... Sorry not true. XP has been known since it first came out to be slow attaining a network if left on auto assign for IP. "Carey Holzman" wrote in message ... Rebuild the Winsock and ensure the DHCP and Network Location Awareness services are running. It's not an XP issue. Thank the spyware on your system. Carey "sdoboze" wrote in message lkaboutsoftware.com... Have the same problem here XPSP2. ATMEL chipset on a 35mw USB adapter. Works fine on many other installations with same router and chipset. This one in particular, "Acquiring network address" forever. Didn't happen under XP SP1. Yet another wonderful microsoft 'feature'. |
Ads |
#17
|
|||
|
|||
Sure - and some don't have a clue what they are talking about. XP *IS* slower to attain a network if left on auto assign and THAT, at least, is a constantly able to be proven fact. "Carey Holzman" wrote in message ... sigh... some people believe men never landed on the moon.... and that the antivirus companies are the ones writing the viruses... Believe what you want, I prefer to believe fact, not fiction. Carey "Interrogative" wrote in message ... Sorry, you are wrong. It is a well known issue. "Carey Holzman" wrote in message ... Not true. "Interrogative" wrote in message ... Sorry not true. XP has been known since it first came out to be slow attaining a network if left on auto assign for IP. "Carey Holzman" wrote in message ... Rebuild the Winsock and ensure the DHCP and Network Location Awareness services are running. It's not an XP issue. Thank the spyware on your system. Carey "sdoboze" wrote in message lkaboutsoftware.com... Have the same problem here XPSP2. ATMEL chipset on a 35mw USB adapter. Works fine on many other installations with same router and chipset. This one in particular, "Acquiring network address" forever. Didn't happen under XP SP1. Yet another wonderful microsoft 'feature'. |
#18
|
|||
|
|||
The error you previously described was that the computer would 'take
forever' waiting to auto-assign an IP address. Of course there will be a slight delay (only measurable with a stop watch) between a static and a dynamic IP address being assigned. However, it is, on a properly configured computer with properly working equipment, done in milliseconds. This, however, was not the 'well known issue' you were referring to, but rather, that Windows will not obtain an address through DHCP. There is no known such issue. Feel free to reply, however, your responses are neither factual or helpful, so I'll be adding you to my ignore list. I'm here to help, not hinder, and further discussion in this manner does not belong in this forum. Carey "Interrogative" wrote in message ... Sure - and some don't have a clue what they are talking about. XP *IS* slower to attain a network if left on auto assign and THAT, at least, is a constantly able to be proven fact. "Carey Holzman" wrote in message ... sigh... some people believe men never landed on the moon.... and that the antivirus companies are the ones writing the viruses... Believe what you want, I prefer to believe fact, not fiction. Carey "Interrogative" wrote in message ... Sorry, you are wrong. It is a well known issue. "Carey Holzman" wrote in message ... Not true. "Interrogative" wrote in message ... Sorry not true. XP has been known since it first came out to be slow attaining a network if left on auto assign for IP. "Carey Holzman" wrote in message ... Rebuild the Winsock and ensure the DHCP and Network Location Awareness services are running. It's not an XP issue. Thank the spyware on your system. Carey "sdoboze" wrote in message lkaboutsoftware.com... Have the same problem here XPSP2. ATMEL chipset on a 35mw USB adapter. Works fine on many other installations with same router and chipset. This one in particular, "Acquiring network address" forever. Didn't happen under XP SP1. Yet another wonderful microsoft 'feature'. |
#19
|
|||
|
|||
"Carey Holzman" wrote in message ... The error you previously described was that the computer would 'take forever' waiting to auto-assign an IP address. Of course there will be a slight delay (only measurable with a stop watch) between a static and a Depends how much you consider "slight" but I have reliably timed it as anything up to 10 minutes in a normal work situation with about 20 odd XP machines, before the machine I was sitting in front of, finally got there. I have repeated that with varying amounts of time, on different installations all over the place, different sizes of networks of course. The machines, themselves and the networking hardware were not in question as they were all working fine. XP just has this unfortunate habit, left on auto, of taking a long time. However, all that is solved by manual assign of IP number. It takes less than 3 seconds on the exact same networks. Feel free to reply, however, your responses are neither factual or helpful, I might say the same to you. It is a well known issue, you say different. You arent helping anyone by continuing the unhelpful info when, with a little more work, their network can be fast to get up and running if they are the type of business who insist on all machines shut down overnight. so I'll be adding you to my ignore list. Yah, good, you do that. It only goes to prove you were wrong and didnt want to know any better. How pathetic of you. I'm here to help, not hinder, and Then HELP and dont add to the worries oif people with your uninformed "help". further discussion in this manner does not belong in this forum. You are wrong there too. It is a networking issue and I have to tell you that you really should know what you are talking about. Get out in the field, work with multiple network and gain knowledge. That will help you to BE help. Until you do, all you are doing is adding RUBBISH as "knowledge" and then refusing to take any other information as truth and refuse to test it. That proves you are someone to be avoided for "help". |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
2 pc network - XP and Win95 - help needed badly! | Clark | Networking and the Internet with Windows XP | 2 | September 3rd 04 11:17 PM |
Network Help | Mackey Freise | Networking and the Internet with Windows XP | 5 | September 2nd 04 05:05 PM |
Network Cable Unplugged Error | Alan | Networking and the Internet with Windows XP | 2 | August 23rd 04 07:36 PM |
ME laptop won't connect with network | Rick | Networking and the Internet with Windows XP | 4 | August 15th 04 04:16 AM |
How do I setup a network | misterxp | Networking and the Internet with Windows XP | 0 | July 16th 04 07:06 PM |