"KG0WX" <(E-Mail Removed)> hath wroth:
>Jeff Liebermann wrote:
>
>>
>> Can you ping the other machines?
>>
>> What happens when you try:
>> Start -> run -> cmd <enter>
>> \\ip_address_of_other_machine
>>
>> Are these other clients connected via wireless or via wired ethernet?
>> If wireless, there is a feature called "AP Isolation" which is used by
>> hot spots to prevent wireless clients from seeing (and attacking) each
>> other. It should be disabled (by default):
>> <http://www.informatione.gmxhome.de/DDWRT/Standard/V23final/Wireless_Advanced.html>
>> (near the middle of the list).
>>
>> Otherwise, look for the usual problems with Windoze firewall
>> exceptions, 3rd part Internet security systems, mixed Windoze
>> workgroups, file sharing disabled, etc.
>> --
>> Jeff Liebermann
>Thanks, Jeff - both the other machines are using the wired portion
>of the router (WRT54g v4). I can ping the 98 machine but get a timeout
>when trying the XP machine. I can ping myself, of course.
Let's take one machine at a time please.
In the XP machine, ping is normally disabled in both the Windoze
firewall exceptions and in your Sygate proxy. You're not going to get
anywhere until you disable BOTH of these. What happens is that you
disable Sygate, which by default, turns on the native Windoze
Firewall. Try to get it to the point where you can ping the XP box
from BOTH other machines.
What happens when you try:
Start -> run -> cmd <enter>
\\ip_address_of_other_machine
This is indpendent of ping and will work even if ping does not.
>AP Isolation is off and I tried turning off the loopback (do I need to
>reboot
>the pc's?) but got no improvement.
I don't know about the loopback suggestion. I've never had to play
with it and have no idea why it would make any difference.
>I tried turning off the Sygate firewall's running on the XP & 2k
>machines
>and made sure F&P sharing was enabled. I also verified that all
>machines
>are spelling the workgroup name (WORKGROUP) identically.
Try removing the wireless from the picture and just plug the wireless
computer into the router with an ethernet cable. Once that's working,
then we can deal with the wireless.
>No success.........
Patience. I think you have a fairly typical mess of Windoze internet
protection software that is doing its best to get in the way. I'm
fairly convinced that the wireless and the router configuration are
correct and have nothing to do with the problem. I'll leave you to
deal with the various computers. It might be something as simple as
not having file and print sharing turned on. What happens when you
browse a computer from itself? You should see your computer name in
"network neighborhood" or whatever XP calls it. If you don't see your
own computer, sharing is off.
I've found it easier to do testing from the command line because of
better error messages. Try:
Start -> run -> cmd <enter>
net view
net view \\ip_address
net view \\netbios_machine_name
net view \\your_own_computer_name
Try these.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558