-=PCTechTalk=- Re: IP address in conflict
- From: Disastar <disastar@xxxxxxxxxxxxx>
- To: pctechtalk@xxxxxxxxxxxxx
- Date: Sun, 01 Mar 2009 01:17:41 -0500
I usually do this simple test first because if the router is wireless it can
be a pain to get the security settings right again. Hmm, unless you were
planning on making a tutorial on properly securing wireless routers??? You
wouldn't believe how many customers a week I get that are running an
unsecured wireless network and I rarely take the time to check since I'm
technically not allowed to make router changes. And when I point it out,
most people just shrug their shoulders and say that it works.
LMAO! You got a good point there. Should probably wear gloves also... I
hate that feeling when you get a BSOD and feel those cold hands grab ya.
Ed
-----Original Message-----
From: pctechtalk-bounce@xxxxxxxxxxxxx
[mailto:pctechtalk-bounce@xxxxxxxxxxxxx] On Behalf Of Gman
Sent: Sunday, March 01, 2009 12:55 AM
To: pctechtalk@xxxxxxxxxxxxx
Subject: -=PCTechTalk=- Re: IP address in conflict
You're on the ball, Ed! :)
That was to be my next approach if the reset didn't help.
By the way, Windows needs socks because it's such a cold hearted OS. lol
Peace,
Gman
http://www.bornagainamerican.org
"The only dumb questions are the ones we fail to ask"
----- Original Message -----
From: "Disastar" <disastar@xxxxxxxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Sunday, March 01, 2009 12:45 AM
Subject: -=PCTechTalk=- Re: IP address in conflict
> Another possibility is the old WinSock problem. Why Windows needs Socks I
> will never understand (lol). The WinSock error is so rare that many tech
> support people never think (or know) about it. Not many people seem to
> know
> how to test for it either, but you're in luck, I do. The easiest way to
> test for it is to go to a command prompt and run a ping test on a website
> (I
> use Google) by URL and another ping test on the website's IP. If the IP
> works but the URL doesn't then you have the WinSock error.
>
> 1) Open command prompt by: click Start, then Run, cmd [ENTER]
> 2) Type (without quotes): ping www.google.com
> 3) Look to see if all the packets Sent were either Received or Lost
> 4) Type (without quotes): ping 66.102.1.147
> 5) Look to see if all the packets Sent were either Received or Lost
>
> If #3 shows all Lost and #5 shows all Received then you have the WinSock
> error. If so, then let us know what version of Windows you have and we
> will
> guide you further on fixing this problem.
>
> Ed
---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To subscribe, unsubscribe or modify your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
To join the PCTableTalk off-topic group, send a blank email to:
pctabletalk+subscribe@xxxxxxxxxxxxxxxx
---------------------------------------------------------------
---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To subscribe, unsubscribe or modify your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
To join the PCTableTalk off-topic group, send a blank email to:
pctabletalk+subscribe@xxxxxxxxxxxxxxxx
---------------------------------------------------------------
Other related posts:
