Often, when you have issues like this, a good practice is to reset TCP/IP
and Winsock. This can especially be true on machines that have been mucked
up with Norton Internet (in)Security, which has an annoying habit of leaving
its firewall settings intact after uninstallation on at least some
versions. This fixes a lot of things at once and so is often a good quick
fix.
The instructions below walk through the process...
Also, check out netstat (open command prompt, do netstat -ano (the n
disables DNS and the o shows the PID). This can give you an idea as to what
sort of connections the computer is making and attempting to make. It also
often reveals viruses, as anything that is trying to spam out or spread
itself out through the network will (generally) show up in here (although,
viruses sometimes do hide themselves).
-Clint Ricker
Kentnis Technologies.
TCP/IP and Winsock Reset
Reset the Winsock and TCP/IP stack... Reset TCP/IP
Command usage netsh int ip reset [log_file_name]
To run the command successfully, you must specify a file name for the log
where actions that are taken by netsh will be recorded. For example, at a
command prompt, type either of the samples that are listed in the "Command
samples" section. The TCP/IP stack will then be reset on a system, and the
actions that were taken will be recorded in the log file, Resetlog.txt. The
first sample creates the log file in the current directory, while the second
sample creates a path where the log will reside. In either case, where the
specified log file already exists, the new log will be appended to the end
of the existing file.
Command samples netsh int ip reset resetlog.txt netsh int ip reset
c:\resetlog.txt
Reset Winsock
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
4. Right-click each key, and then click Delete.
5. Click Yes to confirm the deletion.
Note Restart the computer after you delete the Winsock keys. This action
creates new shell entries for those two registry subkeys. If you do not
restart the computer after you delete the Winsock keys, the next step does
not work correctly. When you restart the computer, you may see dialog boxes
that mention TCP/IP problems and various event log messages that relate to
services that you have installed. Ignore these messages. To reinstall
TCP/IP, follow these steps:
1. Right-click the network connection, and then click Properties.
2. Click Install, click Protocol, and then click Add.
3. Click Have Disk
4. Type C:\Windows\inf, and then click OK.
5. In the list of available protocols, click Internet Protocol
(TCP/IP), and then click OK.
6. Restart the computer.
-----------------
On 5/25/07, Chadd Thompson <[EMAIL PROTECTED]> wrote:
Marlon,
Sound like you covered all your bases here but here is my .02
worth.
I have had issues like this in the past and it has always been related to
one of three things.
1. If it is a new hookup from dialup or SAT usually it is some sort of a
proxy issue, either proxy is enabled in internet explorer settings or
there
is a third party app installed for the dialup/sat. I had to reformat a PC
one time because I couldn't get a clean uninstall of Directway's proxy
software.
2. Mcaffee or Norton Virus/internet security is installed tyring to make
sure that it stays installed on the PC and kept up to date. I have seen
both
programs totally hose a PC with the same issues you are describing. One of
the first things I do on a PC with either of these to programs is
uninstall
it "if it will let you" and install AVG Antivirus and AVG anitspyware or
MS
defender.
3. There is a virus and or spyware on the PC.
Thanks,
Chadd
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Marlon K. Schafer (509) 982-2181
> Sent: Friday, May 25, 2007 1:35 PM
> To: wireless@wispa.org
> Cc: [EMAIL PROTECTED]
> Subject: [WISPA] strange connectivity issues
>
>
> I've had some very strange things happen of late.
>
> Wed. I hooked up a new customer. Couldn't get their system to
> work but my
> laptop did. I told them to call MacAfee and see if they could figure
out
> what was blocking things. They ended up taking the computer to a
> friend's
> house, hooking it up to a dsl connection via a router and it worked just
> fine. Why would it not work via static ip but would via dhcp?
>
> Yesterday I did a Vista setup. It would connect to the wireless
> router just
> fine but would not get to the internet. I finally went into IE
> options and
> set all of them back to the defaults. What BS would have been in IE
that
> would have told it to not use the established network connection? There
> were no proxy's set up either. Worked with the same router and wildblue
> sat. connection. I changed the wireless network name and local ip addy.
> Nothing else changed. It still says that the DNS suffix is
> wildblue.net. I
> can't find that anywhere in the machine. Oh yeah, the machine
> had both IE
> and firefox, neither worked.
>
> Vista is a disaster. Crappy interface. Hides everything in
> strange places
> and in non intuitive fashion.
>
> Today I get an email from a customer that can email but IE won't
> work. This
> one's dialup.
>
> Anyone else seeing strange stuff like this? Is there some
> bizarre windows
> update or virus program that's messing things up?
>
> Marlon
> (509) 982-2181
> (408) 907-6910 (Vonage) Consulting services
> 42846865 (icq) WISP Operator
> since 1999!
> [EMAIL PROTECTED]
> www.odessaoffice.com/wireless
> www.odessaoffice.com/marlon/cam
>
>
>
> --
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date:
> 5/24/2007 4:01 PM
>
--
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
