Re: Difficult Problem - Internet Access Issue



Sorry I haven't gotten back on this. I did get the ISP DNS server IP and
that did not work either. I feel a bit dense on this one but I finally just
connected the cable modem directly to the computer, removing it from my LAN
and it worked fine.
I suspect some network or rounter issue but that is very wierd since all my
other workstations (5) can access the server, other workstations and the
internet just fine????

Thanks both of you for your your help! - Jody

"Scott Ford" wrote:

> Try just using a random public DNS server, one that you can ping from your
> good machine. THis soundslike a DNS problem all the way to me.
>
> "Jody" wrote:
>
> > I had to email my ISP they dont have that info posted on their website. I
> > will get back to you when Ihave tested that.
> >
> > Question: If that doe snot work then what?
> >
> > Thank you very much for your help. I appreciate it greately.
> >
> > "Pegasus (MVP)" wrote:
> >
> > > Ask your ISP. Some ISPs publish their DNS address on their
> > > web page.
> > >
> > >
> > > "Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:65ADB72C-4D77-4D13-A54D-4BE8641FE192@xxxxxxxxxxxxxxxx
> > > > Tried 192.168.1.1 Didn't work
> > > > Tried the NS1 IP for the ISP's webiste domain is that what you mean? That
> > > > did not work either. If that is not the correct IP then how do I find out
> > > > what my ISP's DNS IP is?
> > > >
> > > > "Pegasus (MVP)" wrote:
> > > >
> > > > > You have several options:
> > > > > - Set the DSN values of the bad machine the same way
> > > > > as for the good machine.
> > > > > - Add 192.168.1.1 as the second DNS address on the bad machine.
> > > > > - Add aaa.bbb.ccc.ddd as the second DNS address on the bad
> > > > > machine, where aaa.bbb.ccc.ddd is the IP address of your ISP's
> > > > > domain name server.
> > > > >
> > > > > "Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > news:66F97CDB-BADD-43DB-BBB5-1DBF2F109443@xxxxxxxxxxxxxxxx
> > > > > > Can sucessfully ping ALL IP's from both good and bad machines
> > > > > > CAN NOT ping FQDN for google on Bad machine.
> > > > > > I get "Unknown host www.google.com."
> > > > > >
> > > > > > Sounds like a resolution problem - what's the fix for that?
> > > > > >
> > > > > > "Pegasus (MVP)" wrote:
> > > > > >
> > > > > > > Your tests prove that both machines can successfully
> > > > > > > ping your default gateway (presumably your router).
> > > > > > > This means that there is nothing wrong with the TCP/IP
> > > > > > > stack, the network adapters, cabling, and the router
> > > > > > > ports.
> > > > > > >
> > > > > > > Here are the next tests I would run:
> > > > > > > - Ping the good machine from the bad machine and
> > > > > > > vice versa, observing the network adapter status
> > > > > > > panels.
> > > > > > > - Ping this address from each machine: 66.102.7.99 (Google).
> > > > > > > - Ping www.google.com from each machine.
> > > > > > >
> > > > > > > What do you get in each case?
> > > > > > >
> > > > > > >
> > > > > > > "Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > > > news:4F4982CA-2A07-409E-B9E1-0CA5FC4CAAF8@xxxxxxxxxxxxxxxx
> > > > > > > > OK -
> > > > > > > > Changed NICs already - same results on both.
> > > > > > > > Just Changed Cable & Hub port - Same
> > > > > > > > No Firewall installed
> > > > > > > > Ping Output:
> > > > > > > >
> > > > > > > > Pinging 192.168.1.1 with 32 bytes of data: - GOOD MACHINE Auto &
> > > Full
> > > > > > > Duples
> > > > > > > > only options Set to Auto
> > > > > > > >
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > >
> > > > > > > > Ping statistics for 192.168.1.1:
> > > > > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > > > > Approximate round trip times in milli-seconds:
> > > > > > > > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> > > > > > > >
> > > > > > > > Pinging 192.168.1.1 with 32 bytes of data: - BAD MACHINE Set to 10
> > > > > Halft
> > > > > > > > Duplex
> > > > > > > > (NOTE: Sometimes I get a couple of Request Timeouts here)
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > > Reply from 192.168.1.1: bytes=32 time<10ms TTL=150
> > > > > > > >
> > > > > > > > Ping statistics for 192.168.1.1:
> > > > > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > > > > Approximate round trip times in milli-seconds:
> > > > > > > > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> > > > > > > >
> > > > > > > > "Pegasus (MVP)" wrote:
> > > > > > > >
> > > > > > > > > In just about all cases, your type of problem is caused
> > > > > > > > > by a firewall. Now I know that you said you don't have
> > > > > > > > > one but I have to state this observation regardless. ZoneAlarm,
> > > > > > > > > for example, is notorious for blocking pings even when
> > > > > > > > > disabled. Uninstallation seems to be required to get things
> > > > > > > > > going.
> > > > > > > > >
> > > > > > > > > Your IP settings look fine. Here is what I would do:
> > > > > > > > > - Set the network adapter speed to 10 MBits/s half duplex
> > > > > > > > > on both PCs during the tests.
> > > > > > > > > - Open the network adapter status display on both machines
> > > > > > > > > so that I can observe the packet counters.
> > > > > > > > > - Ping 192.168.1.1 on the good machine. The packets must
> > > > > > > > > be visible on the status display.
> > > > > > > > > - Ping 192.168.1.1 on the bad machine. The packets must
> > > > > > > > > be visible on the status display.
> > > > > > > > > - If not then I would uninstall and re-install the TCP/IP
> > > protocol,
> > > > > > > > > change the network cable, replace the network adapter,
> > > > > > > > > change the hub/switch port.
> > > > > > > > >
> > > > > > > > > "Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > > > > > news:06E095BF-7BA3-4960-ABDC-BA2B4F30695A@xxxxxxxxxxxxxxxx
> > > > > > > > > > Windows 2000 IP Configuration - GOOD MACHINE
> > > > > > > > > > Host Name . . . . . . . . . . . . : mce5-Laptop
> > > > > > > > > > Primary DNS Suffix . . . . . . . :
> > > > > > > > > > Node Type . . . . . . . . . . . . : Broadcast
> > > > > > > > > > IP Routing Enabled. . . . . . . . : No
> > > > > > > > > > WINS Proxy Enabled. . . . . . . . : No
> > > > > > > > > > Ethernet adapter Local Area Connection 2:
> > > > > > > > > > Connection-specific DNS Suffix . :
> > > > > > > > > > Description . . . . . . . . . . . : 3Com Megahertz 10/100 LAN
> > > > > CardBus
> > > > > > > PC
> > > > > > > > > > Card #2
> > > > > > > > > > Physical Address. . . . . . . . . : 00-50-DA-D2-53-DC
> > > > > > > > > > DHCP Enabled. . . . . . . . . . . : No
> > > > > > > > > > IP Address. . . . . . . . . . . . : 192.168.1.107
> > > > > > > > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > > > > > > > Default Gateway . . . . . . . . . : 192.168.1.1
> > > > > > > > > > DNS Servers . . . . . . . . . . . : 192.168.1.105
> > > > > > > > > >
> > > > > > > > > > Windows 2000 IP Configuration - BAD MACHINE
> > > > > > > > > > Host Name . . . . . . . . . . . . : brooks
> > > > > > > > > > Primary DNS Suffix . . . . . . . :
> > > > > > > > > > Node Type . . . . . . . . . . . . : Broadcast
> > > > > > > > > > IP Routing Enabled. . . . . . . . : No
> > > > > > > > > > WINS Proxy Enabled. . . . . . . . : No
> > > > > > > > > > Ethernet adapter Local Area Connection 2:
> > > > > > > > > > Connection-specific DNS Suffix . :
> > > > > > > > > > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI
> > > Adapter
> > > > > > > > > > Physical Address. . . . . . . . . : 00-50-BA-5D-C8-92
> > > > > > > > > > DHCP Enabled. . . . . . . . . . . : No
> > > > > > > > > > IP Address. . . . . . . . . . . . : 192.168.1.112
> > > > > > > > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > > > > > > > Default Gateway . . . . . . . . . : 192.168.1.1
> > > > > > > > > > DNS Servers . . . . . . . . . . . : 198.162.1.105
> > > > > > > > > >
> > > > > > > > > > "Pegasus (MVP)" wrote:
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Jody" <Jody@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > > > > > > > news:4F6F46E3-9572-4A1A-8C1D-FC9E8DC14CD7@xxxxxxxxxxxxxxxx
> > > > > > > > > > > > I have a client who has an HP Pavilion 531W that
> > > originally
> > > > > had XP
> > > > > > > > > Home.
> > > > > > > > > > > The
> > > > > > > > > > > > machine was so clogged with spyware that I had no choice
> > > but
> > > > > to
> > > > > > > run a
> > > > > > > > > > > > destructive restore from the hard drive.
> > > > > > > > > > > >
> > > > > > > > > > > > The destructive restore did not solve the performance
> > > problems
> > > > > and
> > > > > > > I
> > > > > > > > > > > thought
> > > > > > > > > > > > perhaps the spyware (1000's + incidents) may have
> > > corrupted
> > > > > the
> > > > > > > > > restore
> > > > > > > > > > > > files. The System Restore CD's that shipped with the
> > > machine
> > > > > > > could
> > > > > > > > > not be
> > > > > > > > > > > > found and they are no longer available from HP. So, I
> > > decided
> > > > > to
> > > > > > > put
> > > > > > > > > > > Windows
> > > > > > > > > > > > 2000 SP4 on the machine since HP told me that "should"
> > > work.
> > > > > > > > > > > >
> > > > > > > > > > > > A fresh W2k install did solve the performance issues
> > > except
> > > > > for
> > > > > > > > > accessing
> > > > > > > > > > > > the internet. It behaves just like when XP was on the
> > > > > machine.
> > > > > > > > > > > >
> > > > > > > > > > > > Before the spyware problems the machine worked with DSL
> > > just
> > > > > fine.
> > > > > > > I
> > > > > > > > > am
> > > > > > > > > > > now
> > > > > > > > > > > > trying to get on the internet with in a cable broadband
> > > > > connection
> > > > > > > via
> > > > > > > > > my
> > > > > > > > > > > > LAN.
> > > > > > > > > > > >
> > > > > > > > > > > > Here are the symptoms and corrective action I have taken
> > > thus
> > > > > far.
> > > > > > > > > Note:
> > > > > > > > > > > > there is NOTING loaded on this machine except the W2K OS -
> > > no
> > > > > > > > > firewall.
> > > > > > > > > > > >
> > > > > > > > > > > > What DOES works:
> > > > > > > > > > > > 1. Can ping the loop back IP
> > > > > > > > > > > > 2. Can ping the Router IP: (NO filtering configured on
> > > router)
> > > > > > > > > > > > 3. I can see the workgroup from another machine on the LAN
> > > > > > > > > > > >
> > > > > > > > > > > > What DOES NOT Work:
> > > > > > > > > > > > 1. Can not ping other machines on the network
> > > > > > > > > > > > 2. Can not ping websites.
> > > > > > > > > > > > 3. Cannot ping this machine from another machine
> > > > > > > > > > > > 4. Browser retunes "Page can not be displayed" for Google
> > > &
> > > > > Yahoo
> > > > > > > etc.
> > > > > > > > > > > > 5. Clicking on the Workgroup from another client on the
> > > LAN I
> > > > > get
> > > > > > > a
> > > > > > > > > > > > "Workgroup is not accessible"."device is not connected"
> > > error
> > > > > > > message.
> > > > > > > > > > > >
> > > > > > > > > > > > What I have TRIED:
> > > > > > > > > > > > 1. Verified the cable is good
> > > > > > > > > > > > 2. Tried 2nd Known good NIC (vs. onboard one)
> > > > > > > > > > > > 3. Uninstalled and Re-installed the IP stack
> > > > > > > > > > > > 4. Set the Browser Connection to LAN and tried
> > > "Automatically
> > > > > > > detect
> > > > > > > > > > > > settings" enabled and un-enabled.
> > > > > > > > > > > > 5. Cleared browser cache
> > > > > > > > > > > > 6. Tried TCP/IP settings to grab IP's dynamically AND also
> > > > > tried
> > > > > > > > > setting
> > > > > > > > > > > > static IP's
> > > > > > > > > > > >
> > > > > > > > > > > > REALLY BIZAR is when I boot the machine one of the boot
> > > > > options
> > > > > > > listed
> > > > > > > > > > > under
> > > > > > > > > > > > Microsoft Windows 2000 Professionals is "Microsoft Windows
> > > > > > > Whistler
> > > > > > > > > > > > Personal" If you try it there is an error and it won't
> > > let
> > > > > you
> > > > > > > boot
> > > > > > > > > to
> > > > > > > > > > > that.
> > > > > > > > > > > > I have NEVER seen that and do not know where that came
> > > from.
> > > > > I
> > > > > > > > > installed
> > > > > > > > > > > W2k
> > > > > > > > > > > > of the same CD' I have used many times. ???
> > > > > > > > > > > >
> > > > > > > > > > > > I feel like I a missing something really obvious and
> > > stupid or
> > > > > > > there
> > > > > > > > > is
> > > > > > > > > > > > something really strange going on with this machine.
> > > Since I
> > > > > have
> > > > > > > had
> > > > > > > > > two
> > > > > > > > > > > > OS's on the machine I would think it would be hardware but
> > > I
> > > > > have
> > > > > > > > > verified
> > > > > > > > > > > > all of that, drivers too.
> > > > > > > > > > > >
> > > > > > > > > > > > I am really at a loss here and would appreciate some help!
> > > > > > > > > > > > Thanks - Jody
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > As a starting point I suggest you post the output from the
> > > > > command
> > > > > > > > > > >
.



Relevant Pages

  • Re: Win2k3 DNS
    ... >own proxy DNS server to the rest of Internet; ... my other ISP. ... >customers exceeds the size alloted to the cache. ... >am using my own resolving proxy DNS server rather than the proxy DNS ...
    (microsoft.public.windows.server.dns)
  • Re: Revers Lookup Path
    ... If that's not your ISP then you will still have to raise it with your ISP because you won't be able to deal with anyone upstream from your ISP. ... So if you use a tool to find it, it first goes to the DNS server you use and asks it for the answer, if that is authoritative for the zone it will return the answer immediately. ... Server 1 is outside our domain in a data center and is the primare DNS server for the registered domain. ... This will become the new Primary DNS server at the domain authority. ...
    (microsoft.public.windows.server.dns)
  • Re: Rejecting Broadband Sevice
    ... As it happens, I think that this issue is resolved now and am looking for a new ISP, so I will look at what BeUnlimited have to offer. ... BTW, I think that you have hit the nail on the head with the DNS Server comment, as I was thinking along the same lines. ... with download speeds always being the same as my line speed ... 24Mbps if you are close to a suitable exchange). ...
    (uk.legal)
  • Re: Netsurf timing out
    ... of ISP hosts automatically through the ... IP address of their DNS server. ... If your router uses fixed values for the IP addresses of the DNS ... all their customers will ...
    (comp.sys.acorn.networking)
  • Re: Best E-mail practices for SBS 2k3?
    ... Our e-mail is hosted through the same company that hosts are website. ... ISP that we use is seperate from that company. ... I tried to setup a reverse DNS entry on my DNS server, ... If that host is your ISP then they should ...
    (microsoft.public.windows.server.sbs)