home network not networking

[Guest]

I just installed a home wireless network. I can access the internet and my e-mail, but I can't see the other machines on the network, hence no file sharing. Can someone help?

 

[Chuck]

I just installed a home wireless network. I can access the internet and my e-mail, but I can't see the other machines on the network, hence no file sharing. Can someone help?

John,

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Label each ipconfig with name and version of operating system.

Are you running both Client for Microsoft Networks, and File and Printer Sharing
for Microsoft Networks (Local Area Connection - Properties), on all computers?
Do you have shares setup on each?

Are you running NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP
- Properties - Advanced - WINS) on all computers?

Make sure the browser service is running on each computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser service is
started.

On any XP Pro system, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have the SFS settings set properly on each computer.

If SFS is disabled, check the Local Security Policy (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

If you set the Local Security Policy to "Guest only", make sure that the Guest
account is enabled, and has an identical, non-blank, password on all computers.
If "Classic", setup and use a common account with identical, non-blank, password
on all computers.

Do any of the computers have a software firewall (ICF or third party)? If so,
you need to configure them for file sharing, by opening ports TCP 139, 445 and
UDP 137, 138, 445, and / or by identifying the other computers as present in the
Local (Trusted) zone. Firewall configurations are a very common cause of
(network) browser, and file sharing, problems.

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

 

[Guest]

Chuck

Yes, I am running both Client for Microsoft Networks and File and Printer Sharing.

If I copy this information into Notepad and publish on this site, doesn't it leave my network vulnerable?

JOhn

 

[Chuck]

Chuck

Yes, I am running both Client for Microsoft Networks and File and Printer Sharing.

If I copy this information into Notepad and publish on this site, doesn't it leave my network vulnerable?

JOhn

John,

The only thing that would make your network vulnerable would be your WAN
address. That is not part of the ipconfig data, and is known only to your
router. And the WAN address is not pertinent to your problem.

OTOH, John, please don't contribute to the spread, and success, of email address
mining viruses. Learn to munge your email address properly, to keep yourself a
bit safer when posting to open forums. Protect yourself and the rest of the
internet - never post your address unmunged.
http://www.mailmsg.com/SPAM_munging.htm

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

 

[Steve Winograd [MVP]]

I just installed a home wireless network. I can access the internet and my e-mail, but I can't see the other machines on the network, hence no file sharing. Can someone help?

1. Permanently disable XP's built-in Internet Connection Firewall on
local area network connections -- it's for use only on a direct modem
connection to the Internet. Disable and un-install all other firewall
programs while troubleshooting. When un-installing a firewall
program, use the un-install procedure provided by the manufacturer .
Don't use Control Panel | Add or Remove Programs, which might not
completely un-install it.

For more information, see:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/sharing/xp/ic_firewall.htm

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Dennis]

I also had a problem getting networking up and running between a Win98 and
WinXP computer. One thing I did that seemed to make it all click was to add
"NET-BEUI" to the TCP protocol on my WinXP computer. It didn't come already
installed, so I had to get it off the installation CD. Found the info on
the web doing a search, but sorry to say, I didn't save the link. Hope this
helps.
dcz
my e-mail, but I can't see the other machines on the network, hence no file
sharing. Can someone help?

 

[Guest]

Here is the info you requested. BTW, the local area connection has a red X and says network cable unplugged


Windows IP Configuratio


Host Name . . . . . . . . . . . . : JohnnyAc

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknow

IP Routing Enabled. . . . . . . . : N

WINS Proxy Enabled. . . . . . . . : N


Ethernet adapter Wireless Network Connection


Connection-specific DNS Suffix . : dc.dc.cox.ne

Description . . . . . . . . . . . : Wireless-G Notebook Adapter ver.4.

Physical Address. . . . . . . . . : 00-0F-66-2E-15-A

Dhcp Enabled. . . . . . . . . . . : Ye

Autoconfiguration Enabled . . . . : Ye

IP Address. . . . . . . . . . . . : 192.168.1.10

Subnet Mask . . . . . . . . . . . : 255.255.255.

Default Gateway . . . . . . . . . : 192.168.1.

DHCP Server . . . . . . . . . . . : 192.168.1.

DNS Servers . . . . . . . . . . . : 68.100.16.2

68.100.16.3

68.9.16.3

Lease Obtained. . . . . . . . . . : Monday, May 17, 2004 5:35:32 P

Lease Expires . . . . . . . . . . : Tuesday, May 18, 2004 5:35:32 P


Ethernet adapter Local Area Connection


Media State . . . . . . . . . . . : Media disconnecte

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NI

Physical Address. . . . . . . . . : 00-08-02-4C-35-6

 

[Chuck]

Here is the info you requested. BTW, the local area connection has a red X and says network cable unplugged.

<SNIP ipconfig for one computer>

John,

OK, that's one computer. How many computers do you have? Do the other ones
have both wired and wireless connectors too? If you could provide ipconfig for
each computer, this would go a lot faster.

Can you access the internet from JohnnyAce with the red X showing?

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

 

[Guest]

So sorry. Yes, two computers. The red X applies to local area connection. Wireless area connection is fine. Internet reception is fine

Here is info on 2nd computer


Windows IP Configuratio


Host Name . . . . . . . . . . . . : Bet

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknow

IP Routing Enabled. . . . . . . . : N

WINS Proxy Enabled. . . . . . . . : N


Ethernet adapter Local Area Connection


Media State . . . . . . . . . . . : Media disconnecte

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connectio

Physical Address. . . . . . . . . : 00-0C-F1-B1-AE-1


Ethernet adapter Wireless Network Connection


Connection-specific DNS Suffix . : dc.dc.cox.ne

Description . . . . . . . . . . . : Wireless-G PCI Adapte

Physical Address. . . . . . . . . : 00-0C-41-65-BA-6

Dhcp Enabled. . . . . . . . . . . : Ye

Autoconfiguration Enabled . . . . : Ye

IP Address. . . . . . . . . . . . : 192.168.1.10

Subnet Mask . . . . . . . . . . . : 255.255.255.

Default Gateway . . . . . . . . . : 192.168.1.

DHCP Server . . . . . . . . . . . : 192.168.1.

DNS Servers . . . . . . . . . . . : 68.100.16.2

68.100.16.3

68.9.16.3

Lease Obtained. . . . . . . . . . : Tuesday, May 18, 2004 6:50:14 P

Lease Expires . . . . . . . . . . : Wednesday, May 19, 2004 6:50:14 P

 

[Chuck]

So sorry. Yes, two computers. The red X applies to local area connection. Wireless area connection is fine. Internet reception is fine.

John,

Ipconfig data looks normal. Two computers, two network adapters each - one
wired and one wireless. Both with the wireless adapter operational, with
autoconfig on, and getting all settings from the router.

Do either of the computers have a software firewall (ICF or third party)? If
so, you need to configure them for file sharing, by opening ports TCP 139, 445
and UDP 137, 138, 445, and / or by identifying the other computers as present in
the Local (Trusted) zone. Firewall configurations are a very common cause of
(network) browser, and file sharing, problems.

Make sure the browser service is running on each computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser service is
started.

Or try some more diagnostics.

From each computer, verify connectivity (substitute computer name or ip address
appropriately) from a command window:
1) Ping the other by name. "ping computer >>c:\ping.txt"
2) Ping the other by ip address. "ping ip >>c:\ping.txt"
3) Ping itself by name. "ping computer >>c:\ping.txt"
4) Ping itself by ip address. "ping ip >>c:\ping.txt"
5) Ping 127.0.0.1. "ping 127.0.0.1 >>c:\ping.txt"
6) Ping the router. "ping 192.168.1.1 >>c:\ping.txt"
Open c:\ping.txt in Notepad, copy and paste into your next post. For both
computers, please.

Provide static route tables for each computer.
Start - Run - "cmd". Type "route print >c:\route.txt" into the command window -
Open c:\route.txt in Notepad, copy and paste into your next post.

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

 

[Guest]

And the route info

==========================================================================
Interface Lis
0x1 ........................... MS TCP Loopback interfac
0x2 ...00 0f 66 2e 15 ad ...... Wireless-G Notebook Adapter ver.4.0 - Packet Scheduler Minipor
0x10004 ...00 08 02 4c 35 6e ...... Realtek RTL8139 Family PCI Fast Ethernet NI
==========================================================================
==========================================================================
Active Routes
Network Destination Netmask Gateway Interface Metri
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 2
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 2
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 2
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 2
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 2
255.255.255.255 255.255.255.255 192.168.1.100 10004
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100
Default Gateway: 192.168.1.
==========================================================================
Persistent Routes
Non

 

[Guest]

Here is info for first computer


Pinging Beth [192.168.1.101] with 32 bytes of data


Reply from 192.168.1.101: bytes=32 time=1ms TTL=12

Reply from 192.168.1.101: bytes=32 time=1ms TTL=12

Reply from 192.168.1.101: bytes=32 time=1ms TTL=12

Reply from 192.168.1.101: bytes=32 time=1ms TTL=12


Ping statistics for 192.168.1.101

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds

Minimum = 1ms, Maximum = 1ms, Average = 1m

Ping request could not find host ip. Please check the name and try again


Pinging JohnnyAce [192.168.1.100] with 32 bytes of data


Reply from 192.168.1.100: bytes=32 time<1ms TTL=12

Reply from 192.168.1.100: bytes=32 time<1ms TTL=12

Reply from 192.168.1.100: bytes=32 time<1ms TTL=12

Reply from 192.168.1.100: bytes=32 time<1ms TTL=12


Ping statistics for 192.168.1.100

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds

Minimum = 0ms, Maximum = 0ms, Average = 0m

Ping request could not find host ip. Please check the name and try again


Pinging 192.168.1.1 with 32 bytes of data


Reply from 192.168.1.1: bytes=32 time=1ms TTL=15

Reply from 192.168.1.1: bytes=32 time=1ms TTL=15

Reply from 192.168.1.1: bytes=32 time=1ms TTL=15

Reply from 192.168.1.1: bytes=32 time=1ms TTL=15


Ping statistics for 192.168.1.1

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds

Minimum = 1ms, Maximum = 1ms, Average = 1m

Ping request could not find host 127.0.01. Please check the name and try again


Pinging 127.0.0.1 with 32 bytes of data


Reply from 127.0.0.1: bytes=32 time<1ms TTL=12

Reply from 127.0.0.1: bytes=32 time<1ms TTL=12

Reply from 127.0.0.1: bytes=32 time<1ms TTL=12

Reply from 127.0.0.1: bytes=32 time<1ms TTL=12


Ping statistics for 127.0.0.1

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds

Minimum = 0ms, Maximum = 0ms, Average = 0m

 

[Guest]

And route info on final machine

==========================================================================
Interface Lis
0x1 ........................... MS TCP Loopback interfac
0x2 ...00 0c f1 b1 ae 14 ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Minipor
0x3 ...00 0c 41 65 ba 63 ...... Wireless-G PCI Adapter - Packet Scheduler Minipor
==========================================================================
==========================================================================
Active Routes
Network Destination Netmask Gateway Interface Metri
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 2
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 2
192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 2
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 2
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 2
255.255.255.255 255.255.255.255 192.168.1.101 2
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101
Default Gateway: 192.168.1.
==========================================================================
Persistent Routes
Non

 

[Guest]

Here is second computer. BTW, browser service is started on each machine.



Pinging johnnyace [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time=4ms TTL=128

Request timed out.

Reply from 192.168.1.100: bytes=32 time=2ms TTL=128

Reply from 192.168.1.100: bytes=32 time=3ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 4ms, Average = 3ms

Ping request could not find host ip. Please check the name and try again.



Pinging Beth [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping request could not find host ip. Please check the name and try again.



Pinging 120.0.0.1 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 120.0.0.1:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms 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 = 1ms, Maximum = 1ms, Average = 1ms



Pinging johnnyace [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time=4ms TTL=128

Reply from 192.168.1.100: bytes=32 time=2ms TTL=128

Reply from 192.168.1.100: bytes=32 time=2ms TTL=128

Reply from 192.168.1.100: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 4ms, Average = 2ms

Ping request could not find host ip. Please check the name and try again.



Pinging Beth [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping request could not find host ip. Please check the name and try again.



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.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:



Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=23ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms 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 = 1ms, Maximum = 23ms, Average = 6ms



Pinging johnnyace [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time=3ms TTL=128

Reply from 192.168.1.100: bytes=32 time=2ms TTL=128

Reply from 192.168.1.100: bytes=32 time=1ms TTL=128

Reply from 192.168.1.100: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 1ms

Ping request could not find host ip. Please check the name and try again.



Pinging Beth [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping request could not find host ip:. Please check the name and try again.



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.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:



Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=1ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms 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 = 1ms, Average = 0ms



Pinging johnnyace [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time=3ms TTL=128

Reply from 192.168.1.100: bytes=32 time=1ms TTL=128

Reply from 192.168.1.100: bytes=32 time=33ms TTL=128

Reply from 192.168.1.100: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 33ms, Average = 9ms

Ping request could not find host ip. Please check the name and try again.



Pinging Beth [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping request could not find host ip. Please check the name and try again.



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.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:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Reply from 192.168.1.1: bytes=32 time=18ms TTL=150

Reply from 192.168.1.1: bytes=32 time<1ms 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 = 18ms, Average = 4ms

 

[Chuck]

And the route info:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 66 2e 15 ad ...... Wireless-G Notebook Adapter ver.4.0 - Packet Scheduler Miniport
0x10004 ...00 08 02 4c 35 6e ...... Realtek RTL8139 Family PCI Fast Ethernet NIC
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 192.168.1.100 10004 1
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None

John,

Just a couple interesting things seen:

1) The ipconfig for Beth shows the wireless card (at that time) using ip
address 192.168.1.103. Yet pinging Beth, from both itself, and from JohnnyAce,
resolves as 192.168.1.101. What does the DHCP table on the router show?

2) What did you type when pinging and you got "Ping request could not find host
ip."? Three times?

Do you have shares setup on both Beth and JohnnyAce? If so, let's find out
exactly what you can't do. Remember to verify each ip address from the router
DHCP table.

From each computer, verify shares visibility (use actual name / address of each
computer as appropriate):
Start - Run then:
1) \\ThisComputerByName
2) \\ThisComputerByIPAddress
3) \\OtherComputerByName
4) \\OtherComputerByIPAddress
Report visibility of shares / error displayed in each test (8 tests total).

Do either Beth or JohnnyAce have a software firewall (ICF or third party)? If
so, you need to configure it for file sharing, by opening ports TCP 139, 445 and
UDP 137, 138, 445, and / or by identifying the other computers as present in the
Local (Trusted) zone. Firewall configurations are a very common cause of
(network) browser, and file sharing, problems.

Since you have a wireless network, a software firewall is a very good idea.
After you get this working, I'll give you some additional security
recommendations.

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