Re: Lost Dialup, Lost LAN

From: Fred Marshall (fmarshallx_at_remove_the_x.acm.org)
Date: 06/21/04


Date: Mon, 21 Jun 2004 07:14:04 -0700

First things first.
Remove all instances of TCP/IP and then add that protocol back.

If you ping a known IP address on the LAN then there should be no reason for
name resolution and the ping program should say:
Pinging 192.168.1.1 with 32 bytes of data.

If the IP address is garbled, that suggests a problem with the ping program
(can't be sure)...

When you set up ICS, you have to set up the ethernet interface to have the
right IP address. Was this done? As I recall, it sets up a bridge and the
bridge takes over those functions..... If not, you may have taken the ICS
computer off the LAN for IP purposes at least... and then you'd not be able
to ping it, etc.....

Also, if you are really connecting the computers with NetBEUI then you may
not be getting a clear picture of the TCP/IP situation. You can find lots
of literature on the web suggesting that *only* TCP/IP is necessary.

You seem to be having problems with the dialup in general. So that would be
a separate investigation.

Fred

"Mat Brown" <matbrown@mindspring.com> wrote in message
news:M1BBc.9100$w07.605@newsread2.news.pas.earthlink.net...
> I have been working on a small office LAN, it is set up as a
workgroup,
> not a domain, all of them running Windows XP, all with static IPs. Each
> computer dials into the internet separately. The first thing that happened
> was one of the computers started having problems with the dialup
connection.
> It would dialup and connect, but there would be no internet there, I could
> not even ping a remote IP. At this point the LAN was still working, so I
> tried setting up Internet Connection Sharing on one of the other computers
> on the LAN. When I was not able to access the internet that way, I
> discovered that I could not even ping the other computers on the LAN. At
> this point I realized that the network also had IPX/SPX enabled, and when
I
> removed it, the computer could not see the rest of the network. It was
after
> this point that I realized that, while the computer could ping loopback
and
> its own IP, when I did, the display was corrupted. It did not show the IP
> address at all, it showed:
> "Pinging ? with 32 bytes of data:"
> Then at the bottom, it showed:
> "Ping statistics for 0ù?:"
> I began suspecting that the TCP/IP had been corrupted. I tried the
> "netsh int ip reset", but that didn't fix anything. By this time I am
ready
> to consider a reformat/reinstall, when I discover that the computer I had
> set up the ICS on is now not able to access the internet either. It dials
up
> and connects to the internet just fine, but there was no internet out
there,
> just like the other one. I quickly checked, and I could still ping other
> computers on the LAN, but I got the same garbage in the ping output. Since
I
> had fed this computer's IP address to the other one in attempting to get
ICS
> working, I began to suspect that there might be a virus of some kind
> involved, moving across the network. The last time the computer had
> successfully been connected to the internet, it had updated McAfee
VirusScan
> to that morning's DAT file, so I ran a full scan of the hard drive.
Nothing.
> So, I am at a loss. It looks like TCP/IP corruption, and so a
> reformat/reinstall would do it. But if I've got something crawling around
> the network, it will just come back. I can't find anything there, but if
> there isn't something, why did the same corruption spread to another
> computer on the network? And, is there an easier way to fix it without
> having to wipe the drive? Has anyone out there seen this before? What is
> going on?
> Thank you for any and all help!
>
>



Relevant Pages

  • Re: natd + ipfw - very slow internet for LAN users
    ... > Ping to an ip address does not use DNS. ... > public internet by using rc.conf statement. ... Some computers are connected in LAN via SWITCH. ... > for LAN users should be good enough, ...
    (freebsd-questions)
  • Re: Unable to establish connection btwn XP and 98se machines sharing router
    ... on the LAN adaptor. ... On the XP machine's NIC to the LAN, I checked the Internet Protocol ... TCP/IP filtering ... you can disable both the Client for Microsoft Networks ...
    (microsoft.public.windowsxp.network_web)
  • Re: Ping not working properly
    ... They are connected to the internet and there is no personal firewall ... I've installed a network printer on the lan however I cannot ... So I did a PING test to x.x.x.68. ...
    (microsoft.public.windowsxp.network_web)
  • Lost Dialup, Lost LAN
    ... It would dialup and connect, but there would be no internet there, I could ... At this point the LAN was still working, ... discovered that I could not even ping the other computers on the LAN. ... this point I realized that the network also had IPX/SPX enabled, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant download anything!!
    ... Internet Explorer file downloads over SSL do not work with the cache control ... Make sure you have loaded TCP/IP. ... Verify network settings by using ping and ipconfig. ... protocol are bound to the dial-up adapter, unbind the protocol so that only ...
    (microsoft.public.windows.inetexplorer.ie6.browser)

Loading