Home Network

aem said:

Can you plaease summarise what's happenning and what needs to happen?

Both pc are wired to the router, so the next logical question is ware they pingable from one another. You're not a noob seekermeister, sorry if it's a dumb question, but i need to get pasted it.

When it comes to networking, I'm about as noob as one can get. I have already posted what is happening as far as I know, and if I knew exactly what needs to happen, I probably wouldn't need to ask questions.

So far as pinging goes, I tried what I found in another thread and ran ping -6 computername in a prompt from the primary computer. When I ran the primary name, it quickly listed results that appeared good. When I ran the secondary's name, it said that it could not find it.

EDIT: Running the same prompts on the secondary, it had the same result pinging itself, but when pinging the primary it said that the destination was unreachable.

aem said:

Well that doesn't add up at all. Both machines are on the same network, and yet only one can ping the other.

Can we see the ipconfig /all details of both machines? Lets disgards all firewall possibilities at the moment.

This is from the primary:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.xxxxxxx>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : xxxxxxx
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ok.cox.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ok.cox.net
Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-15-F2-DB-4D-85
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e56f:aa68:eade:1180%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, January 25, 2010 4:43:41 PM
Lease Expires . . . . . . . . . . : Tuesday, January 26, 2010 4:43:41 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 301995506
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-75-3B-89-00-E0-18-99-88-77

DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.ok.cox.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : ok.cox.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:42d:7d0e:9d4d:55e6(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::42d:7d0e:9d4d:55e6%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

A thought just ran through my head. I have the primary set to use Google's DNS server, and the secondary set to use Cox's DNS server. Would this make a difference?

You will need to use different user names, or I should say that when I used the same user name I couldn't see the other machine. Supposidly the workgroup name doesn't matter for Homegroups but I would set both machines with the same workgroup name.

I would use the same server. I'm not too sure why you need two? Both machines need to be connected by a router using the same modem with the same ISP. It sounds like you are getting the internet from two different sources, but the screens looks like cox only to me.

Forgot to give it for the scondary. Hre it is:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . :xxxxxxxxxx
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ok.cox.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ok.cox.net
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 04-4B-80-80-80-03
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2d6e:d8d1:dca8:7dd2%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.155(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, January 25, 2010 2:18:15 PM
Lease Expires . . . . . . . . . . : Tuesday, January 26, 2010 2:18:15 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 235162496
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-E5-9A-C7-04-4B-80-80-80-03

DNS Servers . . . . . . . . . . . : 68.105.28.12
68.105.29.12
68.105.28.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.ok.cox.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : ok.cox.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:2c35:72b0:9d4d:55e6(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::2c35:72b0:9d4d:55e6%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

chev65 said:

You will need to use different user names, or I should say that when I used the same user name I couldn't see the other machine. Supposidly the workgroup name doesn't matter for Homegroups but I would set both machines with the same workgroup name.

I would use the same server. I'm not too sure why you need two? Both machines need to be connected by a router using the same modem with the same ISP. It sounds like you are getting the internet from two different sources? This was never mentioned before.

I make the changes, but it is not that Ihave different sources, it's just that I never got around to applying the Google DNS on the secondary. They are both on the same router, using the same ISP.

Hmm well they should be able to at least ping each other, sounds like a firewall or something might be blocking it. Maybe resetting the router might help.

I hope there are no anti virus's involved LOL. I just know a third party program must be involved here. Try using different user names.

Rethinking what I said, in a sense they do have different names. Since I'm logged into the built in administrator account on both machines, the account is administrator for both, but with the computer name attached to each. My regular accounts have the same name, but since I'm not logged into them, that shouldn't be an issue...should it?

EDIT: I changed the user accounts name, but the administrator account's name is the same in both computers. I guess administrator is just administrator.