Re: tcp/ip mostly quit working

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Microsoft Support Desk (Support_at_microsoft.com)
Date: 06/20/04 

Date: Sat, 19 Jun 2004 18:09:49 -0700

get rid of linux - use microsoft products only
>-----Original Message-----
>In article <63_Ac.76457$0y.4354@attbi_s03>,
> "Steven L Umbach" <n9rou@nospam-comcast.net> writes:
>>Try entering an IP address in IE address bar such as
207.47.250.119 [Microsoft
>>website] to see if that works which if it does would
indicate a dns problem.
>
>I didn't try this specifically, but I know it won't
work. DNS (name
>resolution) is certainly broken, but its more than that,
because I
>can't telnet by IP address to other local hosts. I tried
a different
>ethernet card, and that didn't make any difference.
>
>>Tracert can also be used to troubleshoot and will show
where a bottleneck is in a routed
>>path.
>
>tracetr works on the local net. I'm assuming it will
work to the
>internet since it uses ping (ICMP) and not UDP or TCP.
>
>> Often repairing winsock will solve the problem. See the
link below for
>>hat. --- Steve
>>
>>http://www.cexx.org/lspfix.htm --- LSP-fix
>
>I'll try this later. Does Win2k still use winsock?
>
>Th+ 70718 Re: tcp/ip mostly quit
working [37]
Steven L Umbach x, Chris
>
>>"Chris Richmond - MD6-FDC ~"
<crichmon@filc8604.fm.intel.com> wrote in message
>>news:cb1pk4$u9e$2@news01.intel.com...
>>> Hi,
>>> I have a w2k pro workstation where most of the
networking stuff
>>> quit working. Its been running just fine for months,
then quit.
>>> Its in my son's room, and I don't think he messed with
anything.
>>> Anyway, its set up with a static address, I'm using a
linux router
>>> for DNS and gateway. There are other PC's that are
working fine.
>>>
>>> What works: ping internal nodes by IP address, network
neighborhood
>>> (I can browse peer systems), ping this host from the
peers.
>>>
>>> What's broken: ping by name, telnet interal nodes by
IP address,
>>> name resolution, anything over the internet, etc.
>>>
>>> What I've tried: verifying all the tcp/ip properties,
attepmting
>>> DHCP (didn't get an address), uninstall reinstall
tcp/ip, reboots,
>>> etc.
>>>
>>> What I don't want to do: reinstall from scratch!
>>>
>>> What is this and what else can I try?
>.
>

Relevant Pages

  • Re: tcp/ip mostly quit working
    ... > get rid of linux - use microsoft products only ... > indicate a dns problem. ... >>can't telnet by IP address to other local hosts. ...
    (microsoft.public.win2000.networking)
  • Re: DNS on a Windows network.
    ... >> server sees all the boxes with their names, but I cannot ping WinXP box ... If so you have a DNS problem, if not, ... You could run that on your Linux system if it's always on. ... > on the Dlink router. ...
    (comp.os.linux.networking)
  • Re: Linux/Windows/Printer problem
    ... Linux on this machine nor print from it. ... this LAN can access ITS files, access the Internet and all the printers. ... The problem that your were having does not sound like a DNS problem to me. ... network, I had internet access. ...
    (uk.comp.os.linux)
  • Re: still cant get ddclient to work
    ... linux, but that seems like a dns problem. ... WARNING: cannot connect to checkip.dyndns.com:80 socket: ...
    (Ubuntu)