Was: Re: Can't get at my own shared files under XP SP2

W

Wendy

So, I was conversing merrily with Chuck last week, but that thread
(http://tinyurl.com/6gd5z) has gone quiet - so I thought that I'd
repost my response, and see if I can raise him...

Chuck - does this look OK?

Also, I've tried to delete this route, but that doesn't happen -
perhaps because it's not in the persistent category?

Network Destination Netmask Gateway Interface
Metric
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 30

Wendy

Here's my response to his last post:

Chuck,

Here's the "route print" output. Very interesting, no?

Wendy

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 11 39 85 d9 ...... Intel(R) PRO/100 VE Network Connection
- Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.3 192.168.0.3 30
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 30
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 30
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None
 
C

Chuck

So, I was conversing merrily with Chuck last week, but that thread
(http://tinyurl.com/6gd5z) has gone quiet - so I thought that I'd
repost my response, and see if I can raise him...

Chuck - does this look OK?

Also, I've tried to delete this route, but that doesn't happen -
perhaps because it's not in the persistent category?

Network Destination Netmask Gateway Interface
Metric
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 30

Wendy

Here's my response to his last post:

Chuck,

Here's the "route print" output. Very interesting, no?

Wendy

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 11 39 85 d9 ...... Intel(R) PRO/100 VE Network Connection
- Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.3 192.168.0.3 30
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 30
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 30
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

Wendy,

Sorry your last post got lost. The news server that I post thru is having
problems this week. :-(

The static route table for 192.168.0.3 looks normal. The entry that you are
looking at is normal, and should not be deleted.
<http://www.microsoft.com/technet/community/columns/cableguy/cg1201.mspx>

Compare your table with a copy of the table from one of my computers.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 04 76 d7 e2 ba ...... 3Com EtherLink XL 10/100 PCI For Complete PC
Management NIC (3C905C-TX) - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.001.1 192.168.001.50 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.001.0 255.255.255.0 192.168.001.50 192.168.001.50 20
192.168.001.50 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.001.255 255.255.255.255 192.168.001.50 192.168.001.50 20
224.0.0.0 240.0.0.0 192.168.001.50 192.168.001.50 20
255.255.255.255 255.255.255.255 192.168.001.50 192.168.001.50 1
Default Gateway: 192.168.001.1
===========================================================================
Persistent Routes:
None

Now, let's start over.

Your original complaint is that you can't browse your workgroup from your
computer. This symptom could have several causes:
- Browser not accessible or not working.
- Name resolution not working.
- Authentication problem.
- Firewall misconfigured.
- Physical network not working.

In a start to diagnosing your problem, we learn that, among other symptoms, your
network connectivity is problematic. Your computer can ping another computer by
ip address successfully. It cannot ping itself, however, nor can the other
computer ping yours.

I presume that there are no observed symptoms with the other computer used to
test yours? We may presume, to start, that there is no problem with the other
computer?

A network connectivity problem like this is very basic, and must be resolved
first. You need to concentrate on the following items:
- Firewall.
- Network configuration.
- Network software.
- Network adapter.
- Cabling.
- Router port.

You have stated that there is no firewall on your computer.

You have provided both the ip configuration, and static route table, listings.
Both look normal.

You have done the TCP/IP reset ("netsh int ip reset"), to no avail.

Now you need to look for physical problems. Swap cable, and router port, with a
known good computer. Check the network card in the computer. See if the
hardware diagnostics provide a clue. Try reloading the drivers, and check to
see if they are the latest available from the vendor. Finally, try another
network card.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
W

Wendy

Chuck,

Did I mention that I can get to the internet and have been posting
from the computer in question?

So, it's not the cable, or the adapter...

You're right about the table - I compared it to another computer here,
and it was the same...

I guess I can try to switch router ports, but DHCP is working, I can
get to the internet, and what doesn't work is pinging myself, which
I'll bet works without any cable connected... (Just tried it on
another computer and that works)...

I've uninstalled (but not physically removed) the ethernet adapter,
rebooted and watched windows reinstall it, but the problem persists.

I'm not sure what else to do... Sounds a heck of a lot like a
misconfiguration on this computer.

Thanks for your help, Chuck, at least I know that it *should* work.

Wendy
 
W

Wendy

OMG!

I'm so sorry to have (sort of) wasted your time - I was so annoyed
about not finding this problem that I took another look - turns out
that I was running a firewall (other than the Windows XP one) and
didn't realize it. I shut it off, and the pinging is back to working.
Fabulous, yes?

Thanks again, for your help...

Wendy
 
C

Chuck

Chuck,

Did I mention that I can get to the internet and have been posting
from the computer in question?

So, it's not the cable, or the adapter...

You're right about the table - I compared it to another computer here,
and it was the same...

I guess I can try to switch router ports, but DHCP is working, I can
get to the internet, and what doesn't work is pinging myself, which
I'll bet works without any cable connected... (Just tried it on
another computer and that works)...

I've uninstalled (but not physically removed) the ethernet adapter,
rebooted and watched windows reinstall it, but the problem persists.

I'm not sure what else to do... Sounds a heck of a lot like a
misconfiguration on this computer.

Thanks for your help, Chuck, at least I know that it *should* work.

Wendy

Wendy,

There is one more possibility. Did you check your Winsock?
http://support.microsoft.com/?id=811259

Give LSP-Fix and WinsockXPFix <http://www.cexx.org/lspfix.htm>, or WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257> a shot.

Don't stop watching this thread though.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
C

Chuck

OMG!

I'm so sorry to have (sort of) wasted your time - I was so annoyed
about not finding this problem that I took another look - turns out
that I was running a firewall (other than the Windows XP one) and
didn't realize it. I shut it off, and the pinging is back to working.
Fabulous, yes?

Thanks again, for your help...

Wendy

Wendy,

Another firewall. Could never have guessed it.

So now get back to the original problem - can you share your files?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
W

Wendy

Chuck,

Everything was fine (I can see the other machines on the network, and
can share files, too) once I took down the Norton Firewall... There
was an entry for the Norton antivirus software in my start menu, and
silly me, I thought that all of the Norton products would live under
the same menu item - and for that or other reasons didn't see the
"Norton Internet Security" entry...

Thanks again.

Wendy.
 
C

Chuck

Chuck,

Everything was fine (I can see the other machines on the network, and
can share files, too) once I took down the Norton Firewall... There
was an entry for the Norton antivirus software in my start menu, and
silly me, I thought that all of the Norton products would live under
the same menu item - and for that or other reasons didn't see the
"Norton Internet Security" entry...

Thanks again.

Wendy.

MP, Wendy. It's wonderful to see a resolution for something so frustrating.

Stay safe.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top