RickC
April 25th 03, 08:37 PM
Ron Lowe,
Thanks for the advice. I will get more detailed here as
to what I did and how I got a work around.
I had the PCs originally on a network which was issueing
IPs from the Linksys router. Both systems got an IP and
the subnet, gateway and DNS was fine. Both system could
browse the lan as well as surf the web. Firewall was
disabled in advance cause we knew we would want sharing
enabled between these two XP stations. After all Windows
updates were installed including drivers we opend up a few
shares. When we tried to browse the network (lan) we
noticed the XP stations only saw themselves (and the other
PCs on the network). Basically neither XP station could
see the other. So I dropped to DOS (command prompt) and
did an IPconfig /all and verified their IPs. I was able
to ping both the loopback (127.0.0.1) and the assigned IP
given to each XP system locally. If I tried to ping xp1
(call them xp1 and xp2 for ease of reading) from xp2 it
would time out. If I did a tracert nothing, time out on
the first hop. The killer here is another XP station on
the network both xp1 and xp2 could ping that system and
the third XP station on our network could ping both xp1
and xp2.
So I took them off the lan and used a cross-over cable and
assigned both xp stations an IP of 192.168.0.1 and
192.168.0.2 with a subnet of 255.255.255.0 to test. Both
systems same problem. Can ping locally just not each
other. I decided to remove/refresh TCP/IP on both systems
rebooted and got the same error.
Now this is where it gets really weird....
I dropped to command prompt and typed in apr -a and
got "no names in cache" or something like that. Every
system I have tried that on in the past comes up with at
least Interface: 192.168.0.x on Interface 0x10000006 or
what ever. Neither of the xp1 or xp2 came up with this.
So what I ended up doing was creating a batch file for
both system that ran something like this
arp -s 192.168.0.1 "ethernet mac address"
arp -s 192.168.0.2 "ethernet mac address"
Just doing it on one system was not enough. After running
this batch file on both system I could ping both system
with out a problem and I can share files now. The only
thing is I STILL do not see Interface: 192.168.0.x on
Interface 0x10000006
Do you think the OS is somehow corrupted? The work around
I used by adding the ARP statements work but this is just
very odd indeed.
Thank you again for your quick response.
>-----Original Message-----
>"RickC" > wrote in message
...
>> Ok, here is the situation. I have two Windows XP
stations
>> freshly installed and firewall disabled. I have
manually
>> assigned an internal IP scheme of 192.168.0.3 and
>> 192.168.0.10 we will call them station1 and station2,
both
>> are in the same workgroup of WG1 and both have a subnet
of
>> 255.255.255.0.
>> I have enabled the guest account and open all sharing
for
>> both systems. What is weird is if I try to ping the
>> systems I get timed out every time. Although both
systems
>> can surf the web and access other stations on the
network
>> as other stations can access the XP stations.
>> After several trials and erros, several cups of coffee
and
>> mats of hair loss I went out on a stretch....
>>
>> I typed in arp -a at the command prompt of both systems
>> and received the same message "no names in cache" or
>> something darn close to that. Humm
>> Ok, then I typed in arp -s 192.168.0.3 "mac address
>> station1" and arp-s 192.168.0.10 "mac address of
station2"
>> I did this on both systems and now they ping everytime,
>> they can also share files, printers..etc. All is
>> wonderful in the world now.
>>
>> Problem is, why is this?!?!?! There has to be a way
>> around this. I am glad I got a work around in the mean
>> time but honestly. How can I get these systems to work
>> properly with having to create a batch file, place it in
>> the startup folder under "all users" so it runs
everytime
>> the PC is booted??
>>
>> Any help with this I cannot thank you enough!!!!!!!
>>
>>
>> Rick
..
Thanks for the advice. I will get more detailed here as
to what I did and how I got a work around.
I had the PCs originally on a network which was issueing
IPs from the Linksys router. Both systems got an IP and
the subnet, gateway and DNS was fine. Both system could
browse the lan as well as surf the web. Firewall was
disabled in advance cause we knew we would want sharing
enabled between these two XP stations. After all Windows
updates were installed including drivers we opend up a few
shares. When we tried to browse the network (lan) we
noticed the XP stations only saw themselves (and the other
PCs on the network). Basically neither XP station could
see the other. So I dropped to DOS (command prompt) and
did an IPconfig /all and verified their IPs. I was able
to ping both the loopback (127.0.0.1) and the assigned IP
given to each XP system locally. If I tried to ping xp1
(call them xp1 and xp2 for ease of reading) from xp2 it
would time out. If I did a tracert nothing, time out on
the first hop. The killer here is another XP station on
the network both xp1 and xp2 could ping that system and
the third XP station on our network could ping both xp1
and xp2.
So I took them off the lan and used a cross-over cable and
assigned both xp stations an IP of 192.168.0.1 and
192.168.0.2 with a subnet of 255.255.255.0 to test. Both
systems same problem. Can ping locally just not each
other. I decided to remove/refresh TCP/IP on both systems
rebooted and got the same error.
Now this is where it gets really weird....
I dropped to command prompt and typed in apr -a and
got "no names in cache" or something like that. Every
system I have tried that on in the past comes up with at
least Interface: 192.168.0.x on Interface 0x10000006 or
what ever. Neither of the xp1 or xp2 came up with this.
So what I ended up doing was creating a batch file for
both system that ran something like this
arp -s 192.168.0.1 "ethernet mac address"
arp -s 192.168.0.2 "ethernet mac address"
Just doing it on one system was not enough. After running
this batch file on both system I could ping both system
with out a problem and I can share files now. The only
thing is I STILL do not see Interface: 192.168.0.x on
Interface 0x10000006
Do you think the OS is somehow corrupted? The work around
I used by adding the ARP statements work but this is just
very odd indeed.
Thank you again for your quick response.
>-----Original Message-----
>"RickC" > wrote in message
...
>> Ok, here is the situation. I have two Windows XP
stations
>> freshly installed and firewall disabled. I have
manually
>> assigned an internal IP scheme of 192.168.0.3 and
>> 192.168.0.10 we will call them station1 and station2,
both
>> are in the same workgroup of WG1 and both have a subnet
of
>> 255.255.255.0.
>> I have enabled the guest account and open all sharing
for
>> both systems. What is weird is if I try to ping the
>> systems I get timed out every time. Although both
systems
>> can surf the web and access other stations on the
network
>> as other stations can access the XP stations.
>> After several trials and erros, several cups of coffee
and
>> mats of hair loss I went out on a stretch....
>>
>> I typed in arp -a at the command prompt of both systems
>> and received the same message "no names in cache" or
>> something darn close to that. Humm
>> Ok, then I typed in arp -s 192.168.0.3 "mac address
>> station1" and arp-s 192.168.0.10 "mac address of
station2"
>> I did this on both systems and now they ping everytime,
>> they can also share files, printers..etc. All is
>> wonderful in the world now.
>>
>> Problem is, why is this?!?!?! There has to be a way
>> around this. I am glad I got a work around in the mean
>> time but honestly. How can I get these systems to work
>> properly with having to create a batch file, place it in
>> the startup folder under "all users" so it runs
everytime
>> the PC is booted??
>>
>> Any help with this I cannot thank you enough!!!!!!!
>>
>>
>> Rick
..