What happens if you try tracert www.yahoo.com from a cmd.exe window (start/run cmd.exe)?

Jim

Jim,

Thank you for the reply.  The response I get is "unable to resolve target system name www.yahoo.com"

 

Do you use a Proxy Server?

No we do not.

Try this: tracert -d 66.218.71.87. That will attempt to trace the route to one of the IP addresses www.yahoo.com uses.

Are you certain that 198.6.1.1 is the correct address of your primary DNS server?

Jim

Jim,

Ran tracert -d 66.218.71.87 and all 30 where timed out.

We have 6 computers in the office.  All but 2 are running 98SE and all use the DNS Primary of 198.6.1.1

Dave

 

Ran tracert -d 66.218.71.87 and all 30 where timed out.

Definitely not primarily a DNS problem, then!

Can any of the machines in the office reach the Internet? If some can and some can't, and the DNS/gateway settings are the same on all of them, you need to sort out the differences between the ones that work and the ones that don't. Given that all can see all the others (that's true, isn't it?), things on the LAN side of the router to the Internet are apparently OK. Does the router have access restrictions of some kind (MAC address, IP address) in place? Is there a network switch or even a firewall that's not allowing traffic from some of the machines to leave the LAN?

Jim

Jim,

All machines in the office are using the internet currently with the same DNS settings.  All machines can see each other, even the problem machine. 

"Does the router have access restrictions of some kind (MAC address, IP address) in place? Is there a network switch or even a firewall that's not allowing traffic from some of the machines to leave the LAN?"

The answer to all the questions you have asked are no.    In addition to rule out the cable I have taken the machine and hooked it up to another cable that was working on one of the other machines, without sucess.  I have replaced the network card, and duplicated all settings on every other 98 se.  Is there anything with the BIOS I am not familiar with.  I do not have any conflicts, and have tried to manually set the IRQ.  I have uninstalled and reinstalled the card and protocols.

Thanks for all your help,

Dave

I can't imagine how this could be a routing issue, given all the things you've tried, but it acts like one. Can you post the output of ipconfig /all and netstat -r from the Win98 machine that has the problem?

To do this, open a command window, enter each command separately, and then copy the results to the clipboard and paste the results into a posting. If the output scrolls, you'll need to "pipe" the output to "more", since Win98 doesn't support scrollback in its command windows.

Like this...

ipconfig /all | more
netstat -r | more

There shouldn't be any privacy issues associated with the output, since all the machines are operating on a network (192.168.60.0/255.255.255.0) that's not routeable on the Internet.

I don't see how this could be a BIOS settings issue, given that the troublesome machine can reach other machines on the LAN.

What model router are you using?

(edit) One more question - can the machine ping the gateway (192.168.60.10)?

Jim

Message Edited by jimw on 12-19-2003 03:14 PM

Jim,

 

Thank you for your reply.

In order of your questions:

Windows 98 IP Configuration

Host Name . . . . . . . . . : Confer

DNS Servers . . . . . . . . : 198.6.1.1

Node Type . . . . . . . . . : Broadcast

NetBIOS Scope ID. . . . . . :

IP Routing Enabled. . . . . : No

WINS Proxy Enabled. . . . . : No

NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.

Physical Address. . . . . . : 44-45-53-54-00-00

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . :

DHCP Server . . . . . . . . : 255.255.255.255

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : NETGEAR FA31X PCI Adapter

Physical Address. . . . . . : 00-09-5B-60-47-72

DHCP Enabled. . . . . . . . : No

IP Address. . . . . . . . . : 192.168.60.12

Subnet Mask . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . : 192.168.60.10

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :

 

C:\>netstat -r

Route Table

Active Routes:

Network Address Netmask Gateway Address Interface Metric

0.0.0.0 0.0.0.0 192.168.60.10 192.168.60.12 1

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.60.0 255.255.255.0 192.168.60.12 192.168.60.12 1

192.168.60.12 255.255.255.255 127.0.0.1 127.0.0.1 1

192.168.60.255 255.255.255.255 192.168.60.12 192.168.60.12 1

224.0.0.0 224.0.0.0 192.168.60.12 192.168.60.12 1

255.255.255.255 255.255.255.255 192.168.60.12 0.0.0.0 1

Active Connections

Proto Local Address Foreign Address State

TCP Confer:1025 DAVE:nbsession TIME_WAIT

Router is a ADTRAN TSU120

I can ping 192.168.60.10

I hope I got everything you asked.  Again, thank you for your time.

Dave

Navin,

 

Yes you are correct. I forgot to uninstall the dial-up adapter, after my last clean sweep of windows.  I just removed it and is still does not work. Here is the result of ipconfig:

Windows 98 IP Configuration

Host Name . . . . . . . . . : Confer

DNS Servers . . . . . . . . : 198.6.1.1

Node Type . . . . . . . . . : Broadcast

NetBIOS Scope ID. . . . . . :

IP Routing Enabled. . . . . : No

WINS Proxy Enabled. . . . . : No

NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : NETGEAR FA31X PCI Adapter

Physical Address. . . . . . : 00-09-5B-60-47-72

DHCP Enabled. . . . . . . . : No

IP Address. . . . . . . . . : 192.168.60.12

Subnet Mask . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . : 192.168.60.10

Primary WINS Server . . . . :

Secondary WINS Server . . . :

Lease Obtained. . . . . . . :

Lease Expires . . . . . . . :

 

Thanks,
Dave

SkyBlue,

Thanks for providing that detailed output. The system has an idle/unassigned PPP adapter and the active Netgear PCI adapter. The routing table looks good. I wanted to make sure there weren't any default routes to anywhere but 192.168.60.10, and there aren't any. The system talks to the rest of the machines on the LAN (192.168.60.0/255.255.255.0) using its own interface - that's entirely as expected, and works.

But there's one more device in the configuration. Unless I've misunderstood Adtran's documentation on the TSU 120, it's a CSU/DSU, not a router. So there's *something* connected to the V.35 interface of the Adtran, and that device is the router.

All the data suggests that the router is blocking all traffic from IP address 192.168.60.12, and not from the MAC address associated with that IP address (since you replaced the network adapter). The fact that you can ping the router's IP address but not pass traffic through it is further evidence that the router is, for some unknown reason, refusing to route traffic from 192.168.60.12.

So you need to clarify what the Adtran's connected to on the V.35 (LAN) side. There's one more piece of hardware in the equation.

Jim

Hi Sky

looks like you have 2  Ethernet adapter's

0 Ethernet adapter  and 1 Ethernet adapter  and one of them dosent have the TCP/IP configured

IP Address. . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . :

Sorry Jim.

It does not help if I do not give you the correct information.

The Router is a Cisco 1700 and the CSU/DSU after the Router is an ADTRAN.

Again just so overwhelmed with this problem.  I have tried changing IP addresses as well if that helps any.

 

Dave

I have tried changing IP addresses as well if that helps any.

That was to have been my next suggestion! I've run out of ideas. It's not the MAC address, it's not the port the machine's connected to, it's obviously not the physical connection, and it's not the IP address the machine's using. Since you're reinstalled SE from scratch, it's unlikely related to the software installation on the machine. One way to rule that out completely is to swap hard drives with another identical system, and see if the problem moves.

If anyone else can spot the problem, please jump in!!!

Jim