GeorgeM said:Yes, the desktops are wired and can each get to the internet but cannot see
each other. What settings do I need to look at?
:
GeorgeM said:Bob - I've checked all the items you listed on my two desktop PCs.
Not sure where to look for IPX/SPX or M$ Nets.
Having a problem pinging self on my main desktop using either name or ip
address. What is the source of this issue?
C:\DOCUME~1\GEORGE>ping office
Pinging OFFICE [192.168.1.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\DOCUME~1\GEORGE>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : OFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter ourhome:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-B2-50-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.154
167.206.3.220
167.206.3.155
Lease Obtained. . . . . . . . . . : Friday, February 11, 2005
10:37:05 A
M
Lease Expires . . . . . . . . . . : Saturday, February 12, 2005
10:37:05
AM
Also - each time I boot this system the network connection gets firewalled -
???
:
Unfortunately, there are lots of settings that could be blocking networking.
Here's some things to check/fix:
1. Set the router as the DHCP server, and set each PC as a DHCP client.
2. Disable all firewalls while debugging your net. XP SP2 enables WF
by default; disable it.
3. Enable TCP/IP and disable all other protocols (IPX/SPX, NetBEUI).
4. Enable NetBIOS over TCP/IP. Enable F&P sharing and Client for M$ Nets.
5. Make sure all PCs have the same workgroup name, and that each has its
own computer name.
6. On each PC, create a folder and share it, with a simple share name.
Can each PC PING itself, by number and by name? Can each PC PING each other,
by number and by name? What does IPCONFIG/ALL report for each?
Bob Willard said:GeorgeM said:Bob - I've checked all the items you listed on my two desktop PCs.
Not sure where to look for IPX/SPX or M$ Nets.
Having a problem pinging self on my main desktop using either name or ip
address. What is the source of this issue?
C:\DOCUME~1\GEORGE>ping office
Pinging OFFICE [192.168.1.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\DOCUME~1\GEORGE>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : OFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter ourhome:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-B2-50-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.154
167.206.3.220
167.206.3.155
Lease Obtained. . . . . . . . . . : Friday, February 11, 2005
10:37:05 A
M
Lease Expires . . . . . . . . . . : Saturday, February 12, 2005
10:37:05
AM
Also - each time I boot this system the network connection gets firewalled -
???
:
GeorgeM wrote:
Yes, the desktops are wired and can each get to the internet but cannot see
each other. What settings do I need to look at?
:
THAT SEEMS TO BE PRETTY MUCH LIKE MY OWN SETTINGS BUT INSTEAD OF THE BEFSR41
I'M USING A DIFFERENT ROUTER ALSO FROM LINKSYS; THE PROBLEM WITH YOUR POST IS
THAT THERE IS NOT ENOUGH INFO ON HOW YOU DID SET YOUR NETWORK; YOU SHOULD TRY
FIRST WITH BOTH DESKTOPS AND ONCE YOU GET THEM WORKING OK THEN TRY TO BRING
UP THE LAPTOP.
ARE YOUR DESKTOPS WIRED?
:
I'm trying to network my desktop computer to another desktop and a laptop in
my home. All the systems are running XP Home Edition SP2. I am using a
Linksys BEFSR41 router. I've tried everything I can find and have no success
in seeing any of the other systems.
Unfortunately, there are lots of settings that could be blocking networking.
Here's some things to check/fix:
1. Set the router as the DHCP server, and set each PC as a DHCP client.
2. Disable all firewalls while debugging your net. XP SP2 enables WF
by default; disable it.
3. Enable TCP/IP and disable all other protocols (IPX/SPX, NetBEUI).
4. Enable NetBIOS over TCP/IP. Enable F&P sharing and Client for M$ Nets.
5. Make sure all PCs have the same workgroup name, and that each has its
own computer name.
6. On each PC, create a folder and share it, with a simple share name.
Can each PC PING itself, by number and by name? Can each PC PING each other,
by number and by name? What does IPCONFIG/ALL report for each?
OK - IPCONFIG confirms that DHCP is working OK. Since you can't PING yourself,
WF is probably enabled (WF = Windows Firewall, the SP2 successor to ICF).
Click on Start, then Help, then enter firewall in the Search box and Enter; that
will lead you (clicking away) to the control panel to disable WF; if Help won't
display the firewall panel because ICS is not running, then you are OK.
If not WF, then I suspect some other firewall is running - you'll need to look
around to see what it is.
As for the net protocols, click on Start, Settings, Control Panel, Network;
right-click on Local Area Connection (that's the normal name), then click on
Properties to display the protocols and APIs in use: you want TCP/IP, Client
for M$ Nets, F&P Sharing; you don't normaly want IPX/SPX (NWLink), NetBEUI, or
TCP/IP v6; QoS doesn't usually matter.
GeorgeM said:OK - making progress - in the properties here is what is enabled:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
Internet Protocol (TCP/IP)
Looks like those are right.
When I checked help on WF it looks like it is set off. This machine is
running Norton - is there something that needs to be set/unset to allow
sharing?
Thanks, George
Bob Willard said:GeorgeM said:Bob - I've checked all the items you listed on my two desktop PCs.
Not sure where to look for IPX/SPX or M$ Nets.
Having a problem pinging self on my main desktop using either name or ip
address. What is the source of this issue?
C:\DOCUME~1\GEORGE>ping office
Pinging OFFICE [192.168.1.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\DOCUME~1\GEORGE>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : OFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter ourhome:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-B2-50-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.154
167.206.3.220
167.206.3.155
Lease Obtained. . . . . . . . . . : Friday, February 11, 2005
10:37:05 A
M
Lease Expires . . . . . . . . . . : Saturday, February 12, 2005
10:37:05
AM
Also - each time I boot this system the network connection gets firewalled -
???
:
GeorgeM wrote:
Yes, the desktops are wired and can each get to the internet but cannot see
each other. What settings do I need to look at?
:
THAT SEEMS TO BE PRETTY MUCH LIKE MY OWN SETTINGS BUT INSTEAD OF THE BEFSR41
I'M USING A DIFFERENT ROUTER ALSO FROM LINKSYS; THE PROBLEM WITH YOUR POST IS
THAT THERE IS NOT ENOUGH INFO ON HOW YOU DID SET YOUR NETWORK; YOU SHOULD TRY
FIRST WITH BOTH DESKTOPS AND ONCE YOU GET THEM WORKING OK THEN TRY TO BRING
UP THE LAPTOP.
ARE YOUR DESKTOPS WIRED?
:
I'm trying to network my desktop computer to another desktop and a laptop in
my home. All the systems are running XP Home Edition SP2. I am using a
Linksys BEFSR41 router. I've tried everything I can find and have no success
in seeing any of the other systems.
Unfortunately, there are lots of settings that could be blocking networking.
Here's some things to check/fix:
1. Set the router as the DHCP server, and set each PC as a DHCP client.
2. Disable all firewalls while debugging your net. XP SP2 enables WF
by default; disable it.
3. Enable TCP/IP and disable all other protocols (IPX/SPX, NetBEUI).
4. Enable NetBIOS over TCP/IP. Enable F&P sharing and Client for M$ Nets.
5. Make sure all PCs have the same workgroup name, and that each has its
own computer name.
6. On each PC, create a folder and share it, with a simple share name.
Can each PC PING itself, by number and by name? Can each PC PING each other,
by number and by name? What does IPCONFIG/ALL report for each?
OK - IPCONFIG confirms that DHCP is working OK. Since you can't PING yourself,
WF is probably enabled (WF = Windows Firewall, the SP2 successor to ICF).
Click on Start, then Help, then enter firewall in the Search box and Enter; that
will lead you (clicking away) to the control panel to disable WF; if Help won't
display the firewall panel because ICS is not running, then you are OK.
If not WF, then I suspect some other firewall is running - you'll need to look
around to see what it is.
As for the net protocols, click on Start, Settings, Control Panel, Network;
right-click on Local Area Connection (that's the normal name), then click on
Properties to display the protocols and APIs in use: you want TCP/IP, Client
for M$ Nets, F&P Sharing; you don't normaly want IPX/SPX (NWLink), NetBEUI, or
TCP/IP v6; QoS doesn't usually matter.
GeorgeM said:I've got it working - I needed to add the IP addresses for the computers to
Norton Networking Trusted list.
Thank you for all your help.
:
OK - making progress - in the properties here is what is enabled:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
Internet Protocol (TCP/IP)
Looks like those are right.
When I checked help on WF it looks like it is set off. This machine is
running Norton - is there something that needs to be set/unset to allow
sharing?
Thanks, George
:
GeorgeM wrote:
Bob - I've checked all the items you listed on my two desktop PCs.
Not sure where to look for IPX/SPX or M$ Nets.
Having a problem pinging self on my main desktop using either name or ip
address. What is the source of this issue?
C:\DOCUME~1\GEORGE>ping office
Pinging OFFICE [192.168.1.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\DOCUME~1\GEORGE>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : OFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter ourhome:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-B2-50-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.154
167.206.3.220
167.206.3.155
Lease Obtained. . . . . . . . . . : Friday, February 11, 2005
10:37:05 A
M
Lease Expires . . . . . . . . . . : Saturday, February 12, 2005
10:37:05
AM
Also - each time I boot this system the network connection gets firewalled -
???
:
GeorgeM wrote:
Yes, the desktops are wired and can each get to the internet but cannot see
each other. What settings do I need to look at?
:
THAT SEEMS TO BE PRETTY MUCH LIKE MY OWN SETTINGS BUT INSTEAD OF THE BEFSR41
I'M USING A DIFFERENT ROUTER ALSO FROM LINKSYS; THE PROBLEM WITH YOUR POST IS
THAT THERE IS NOT ENOUGH INFO ON HOW YOU DID SET YOUR NETWORK; YOU SHOULD TRY
FIRST WITH BOTH DESKTOPS AND ONCE YOU GET THEM WORKING OK THEN TRY TO BRING
UP THE LAPTOP.
ARE YOUR DESKTOPS WIRED?
:
I'm trying to network my desktop computer to another desktop and a laptop in
my home. All the systems are running XP Home Edition SP2. I am using a
Linksys BEFSR41 router. I've tried everything I can find and have no success
in seeing any of the other systems.
Unfortunately, there are lots of settings that could be blocking networking.
Here's some things to check/fix:
1. Set the router as the DHCP server, and set each PC as a DHCP client.
2. Disable all firewalls while debugging your net. XP SP2 enables WF
by default; disable it.
3. Enable TCP/IP and disable all other protocols (IPX/SPX, NetBEUI).
4. Enable NetBIOS over TCP/IP. Enable F&P sharing and Client for M$ Nets.
5. Make sure all PCs have the same workgroup name, and that each has its
own computer name.
6. On each PC, create a folder and share it, with a simple share name.
Can each PC PING itself, by number and by name? Can each PC PING each other,
by number and by name? What does IPCONFIG/ALL report for each?
--
Cheers, Bob
OK - IPCONFIG confirms that DHCP is working OK. Since you can't PING yourself,
WF is probably enabled (WF = Windows Firewall, the SP2 successor to ICF).
Click on Start, then Help, then enter firewall in the Search box and Enter; that
will lead you (clicking away) to the control panel to disable WF; if Help won't
display the firewall panel because ICS is not running, then you are OK.
If not WF, then I suspect some other firewall is running - you'll need to look
around to see what it is.
As for the net protocols, click on Start, Settings, Control Panel, Network;
right-click on Local Area Connection (that's the normal name), then click on
Properties to display the protocols and APIs in use: you want TCP/IP, Client
for M$ Nets, F&P Sharing; you don't normaly want IPX/SPX (NWLink), NetBEUI, or
TCP/IP v6; QoS doesn't usually matter.
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.