Network issues

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to troubleshoot a computer, but I cannot get it online to check
for updates. Here is the configuration:

Cable modem----Comp 1 (What I'm usign now)--=cross-over=---Comp 2.

There is a connection between the 2, but I cannot see the other on the
network via either system. I have deleted the winsock registry files and
reinstalled TCP/IP. I have installed NetBIOS. It won't renew the IP. All
firewalls are shut down (I am NOT uninstalling them. It took me a week to
get them installed and working.)

Comp 2 has a subnet mask of 255.255.0.0
Comp 1 has masks of 255.255.254.0 and 255.255.255.0
 
- I don't understand the physical connection. Cable Modem plugged in to
comp1 via USB? Then network cable from NIC to NIC on each computer? If so,
that sounds really interesting. You would need internet connection sharing
enabled on Comp1, or easiest thing is to get a router to serve the same
purpose.
 
I am trying to troubleshoot a computer, but I cannot get it online to check
for updates. Here is the configuration:

Cable modem----Comp 1 (What I'm usign now)--=cross-over=---Comp 2.

There is a connection between the 2, but I cannot see the other on the
network via either system. I have deleted the winsock registry files and
reinstalled TCP/IP. I have installed NetBIOS. It won't renew the IP. All
firewalls are shut down (I am NOT uninstalling them. It took me a week to
get them installed and working.)

Comp 2 has a subnet mask of 255.255.0.0
Comp 1 has masks of 255.255.254.0 and 255.255.255.0

Drew,

Which computer can't you get online?

If you can't get a computer online, maybe the firewall ISN'T working.

Are you running ICS on Computer 1?

Provide ipconfig information for each computer, so we can see what to look at
next.
Start - Run - "cmd" - Type "ipconfig /all >c:\ipconfig.txt" into the command
window. Open Notepad, make sure that Format - Word Wrap is NOT checked!, open
file c:\ipconfig.txt, copy and paste entire contents into your next post.
Identify operating system (by name, version, and SP level) with each ipconfig
listing.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
The first comp is connected via ethernet cable to cable modem. No USB in use
for connection purposes.

Comp 1 ipconfig:


Windows IP Configuration

Host Name . . . . . . . . . . . . : hal-9000
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-05-1C-98-BA-73
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 64.83.194.168
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 64.83.194.1
DHCP Server . . . . . . . . . . . : 10.20.2.10
DNS Servers . . . . . . . . . . . : 64.83.223.21
64.83.223.20
Lease Obtained. . . . . . . . . . : Friday, March 11, 2005 8:34:39 PM
Lease Expires . . . . . . . . . . : Saturday, March 12, 2005 8:34:39
PM

Ethernet adapter Network Bridge (Network Bridge):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-02-E3-20-9D-E1
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Comp 2 ipconfig:

Windows IP Configuration

Host Name . . . . . . . . . . . . : CATHAINE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Network Bridge (Network Bridge):

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-07-95-E1-54-45
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.159
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, March 11, 2005 8:37:22 PM
Lease Expires . . . . . . . . . . : Friday, March 18, 2005 8:37:22 PM

Comp2 occasionaly saw the internet both with and without Zone Alarm Pro
operating. I currently have the firwall turned off and Comp2 access the net
just fine. I should have ICS activated on Comp1. I had put Comp2's IP in
the Trusted Zone for ZAPro as well as the DNS server addresses. Am I doing
something horribly wrong? Am I being punished because I can't afford a
router? My only other option is a 3-year old hub, and that doesn't transfer
data fast enough for my liking.
 
The first comp is connected via ethernet cable to cable modem. No USB in use
for connection purposes.

Comp2 occasionaly saw the internet both with and without Zone Alarm Pro
operating. I currently have the firwall turned off and Comp2 access the net
just fine. I should have ICS activated on Comp1. I had put Comp2's IP in
the Trusted Zone for ZAPro as well as the DNS server addresses. Am I doing
something horribly wrong? Am I being punished because I can't afford a
router? My only other option is a 3-year old hub, and that doesn't transfer
data fast enough for my liking.

Drew,

If you have broadband, and an Ethernet modem, the absolutely best thing you can
do now is to buy a broadband router. For convenience, performance, and
security, you cannot beat using a router.

I think the bridge on hal-9000 is your problem, with this setup anyway.

If you can't afford a router (and if you can afford broadband and 2 computers
you CAN), you should delete the bridge on hal-9000, and enable ICS to share
internet service with CATHAINE. But you have the setup to use a router.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
The bridge put itself there when I set up ICS. I don't know how, but it IS
currently working. It wasn't a couple days ago. Even through the firewall.

"If you can't afford a router (and if you can afford broadband and 2 computers
you CAN)"

No, I can't afford a router. I am in the poor bracket for income. I make
just enough to keep a roof over my head. They are due to cut my internet
soon. Along with power, phone, cable, etc. It sucks being poor. The 2
comps are ones I cobbled together out of spare parts. Home-built is the only
way to go.

But like I said, I don't know how exactly it has happened, but CATHAINE now
can connect to the internet.
 
The bridge put itself there when I set up ICS. I don't know how, but it IS
currently working. It wasn't a couple days ago. Even through the firewall.

"If you can't afford a router (and if you can afford broadband and 2 computers
you CAN)"

No, I can't afford a router. I am in the poor bracket for income. I make
just enough to keep a roof over my head. They are due to cut my internet
soon. Along with power, phone, cable, etc. It sucks being poor. The 2
comps are ones I cobbled together out of spare parts. Home-built is the only
way to go.

But like I said, I don't know how exactly it has happened, but CATHAINE now
can connect to the internet.

Drew,

OK, it's your dime. You have two computers sort of working. Let's make them
work better.

ICS is a software based router. You typically don't have both a bridge, and a
router, enabled on the same computer. Are you sure that ICS is active?

Your problem is either the firewalls, or the use of the bridge. Both have been
known to cause problems, in various ways, with file sharing. Let's enumerate
your file sharing symptoms, and see if the symptoms indicate a cause.

Take the following code (everything inside the "#####"). (Please verify
computer names and ip addresses).

Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight then
Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V) into
Notepad. Verify, and correct, names and addresses if necessary.
Save the Notepad file as "cdiag.cmd", as type "All Files", into the root folder
"C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
When Notepad opens up displaying c:\cdiag.txt, first check Format and ensure
that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A Ctrl-C)
and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

#####

@echo off
set FullTarget1=hal-9000 192.168.0.1
set FullTarget2=CATHAINE 192.168.0.159
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set PingTargets=127.0.0.1
Set Version=V1.1
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (==> %FullTargets%) >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping www.yahoo.com" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping www.yahoo.com >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping 66.94.230.32" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping 66.94.230.32 >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target - Full %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target - Ping Only %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
For HAL-9000

CDiagnosis V1.1
Start diagnosis for HAL-9000 (== 192.168.0.1 CATHAINE 192.168.0.159 )

"ping www.yahoo.com"



Pinging www.yahoo.akadns.net [216.109.118.74] with 32 bytes of data:



Reply from 216.109.118.74: bytes=32 time=45ms TTL=53

Reply from 216.109.118.74: bytes=32 time=46ms TTL=54

Reply from 216.109.118.74: bytes=32 time=47ms TTL=54

Reply from 216.109.118.74: bytes=32 time=60ms TTL=53



Ping statistics for 216.109.118.74:

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

Approximate round trip times in milli-seconds:

Minimum = 45ms, Maximum = 60ms, Average = 49ms


"ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=77ms TTL=54

Reply from 66.94.230.32: bytes=32 time=79ms TTL=53

Reply from 66.94.230.32: bytes=32 time=79ms TTL=53

Reply from 66.94.230.32: bytes=32 time=77ms TTL=54



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 77ms, Maximum = 79ms, Average = 78ms


Target - Full hal-9000

"ping hal-9000"



Pinging hal-9000 [192.168.0.1] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.1:

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

Approximate round trip times in milli-seconds:

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


"net view hal-9000"

Shared resources at hal-9000

Drew's Gamer

Share name Type Used as Comment

-------------------------------------------------------------------------------
printer Print hp deskjet 3320 series
SharedDocs Disk
The command completed successfully.


Target - Full 192.168.0.1

"ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.1:

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

Approximate round trip times in milli-seconds:

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


"net view 192.168.0.1"

Shared resources at 192.168.0.1

Drew's Gamer

Share name Type Used as Comment

-------------------------------------------------------------------------------
printer Print hp deskjet 3320 series
SharedDocs Disk
The command completed successfully.


Target - Full CATHAINE

"ping CATHAINE"



Pinging CATHAINE [192.168.0.159] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.159:

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

Approximate round trip times in milli-seconds:

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


"net view CATHAINE"

Shared resources at CATHAINE

Amy's Demon Summoner

Share name Type Used as Comment

-------------------------------------------------------------------------------
MUsic Disk
SharedDocs Disk
The command completed successfully.


Target - Full 192.168.0.159

"ping 192.168.0.159"



Pinging 192.168.0.159 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.159:

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

Approximate round trip times in milli-seconds:

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


"net view 192.168.0.159"

Shared resources at 192.168.0.159

Amy's Demon Summoner

Share name Type Used as Comment

-------------------------------------------------------------------------------
MUsic Disk
SharedDocs Disk
The command completed successfully.


Target - Ping Only 127.0.0.1

"ping 127.0.0.1"



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


Shared resources at 127.0.0.1

Drew's Gamer

Share name Type Used as Comment

-------------------------------------------------------------------------------
printer Print hp deskjet 3320 series
SharedDocs Disk
The command completed successfully.

End diagnosis for HAL-9000


For CATHAINE

CDiagnosis V1.1
Start diagnosis for CATHAINE (== 192.168.0.1 CATHAINE 192.168.0.159 )

"ping www.yahoo.com"

Pinging www.yahoo.akadns.net [216.109.118.75] with 32 bytes of data:Reply
from 216.109.118.75: bytes=32 time=56ms TTL=52Reply from 216.109.118.75:
bytes=32 time=46ms TTL=53Reply from 216.109.118.75: bytes=32 time=46ms
TTL=53Reply from 216.109.118.75: bytes=32 time=45ms TTL=52Ping statistics for
216.109.118.75: Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),Approximate round trip times in milli-seconds: Minimum = 45ms,
Maximum = 56ms, Average = 48ms
"ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32
time=76ms TTL=52Reply from 66.94.230.32: bytes=32 time=79ms TTL=53Reply from
66.94.230.32: bytes=32 time=76ms TTL=53Reply from 66.94.230.32: bytes=32
time=81ms TTL=52Ping statistics for 66.94.230.32: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 76ms, Maximum = 81ms, Average = 78ms
Target - Full hal-9000

"ping hal-9000"

Pinging hal-9000.mshome.net [192.168.0.1] with 32 bytes of data:Reply from
192.168.0.1: bytes=32 time<1ms TTL=128Reply from 192.168.0.1: bytes=32
time<1ms TTL=128Reply from 192.168.0.1: bytes=32 time<1ms TTL=128Reply from
192.168.0.1: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"net view hal-9000"

Shared resources at hal-9000

Drew's Gamer

Share name Type Used as Comment

-------------------------------------------------------------------------------
printer Print hp deskjet 3320 series
SharedDocs Disk
The command completed successfully.


Target - Full 192.168.0.1

"ping 192.168.0.1"

Pinging 192.168.0.1 with 32 bytes of data:Reply from 192.168.0.1: bytes=32
time<1ms TTL=128Reply from 192.168.0.1: bytes=32 time<1ms TTL=128Reply from
192.168.0.1: bytes=32 time<1ms TTL=128Reply from 192.168.0.1: bytes=32
time<1ms TTL=128Ping statistics for 192.168.0.1: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"net view 192.168.0.1"

Shared resources at 192.168.0.1

Drew's Gamer

Share name Type Used as Comment

-------------------------------------------------------------------------------
printer Print hp deskjet 3320 series
SharedDocs Disk
The command completed successfully.


Target - Full CATHAINE

"ping CATHAINE"

Pinging CATHAINE [192.168.0.159] with 32 bytes of data:Reply from
192.168.0.159: bytes=32 time<1ms TTL=128Reply from 192.168.0.159: bytes=32
time<1ms TTL=128Reply from 192.168.0.159: bytes=32 time<1ms TTL=128Reply from
192.168.0.159: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"net view CATHAINE"

Shared resources at CATHAINE

Amy's Demon Summoner

Share name Type Used as Comment

-------------------------------------------------------------------------------
MUsic Disk
SharedDocs Disk
The command completed successfully.


Target - Full 192.168.0.159

"ping 192.168.0.159"

Pinging 192.168.0.159 with 32 bytes of data:Reply from 192.168.0.159:
bytes=32 time<1ms TTL=128Reply from 192.168.0.159: bytes=32 time<1ms
TTL=128Reply from 192.168.0.159: bytes=32 time<1ms TTL=128Reply from
192.168.0.159: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"net view 192.168.0.159"

Shared resources at 192.168.0.159

Amy's Demon Summoner

Share name Type Used as Comment

-------------------------------------------------------------------------------
MUsic Disk
SharedDocs Disk
The command completed successfully.


Target - Ping Only 127.0.0.1

"ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32
time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from
127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms
TTL=128Ping 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
Shared resources at 127.0.0.1

Amy's Demon Summoner

Share name Type Used as Comment

-------------------------------------------------------------------------------
MUsic Disk
SharedDocs Disk
The command completed successfully.

End diagnosis for CATHAINE
 
On Sat, 12 Mar 2005 20:09:02 -0800, "Darkdrew"

<SNIP CDiags>

Well, Drew,

Your statement that internet service is now available on CATHAINE apparently
means that you have no problem. At least, none is apparent from the CDiags
which you ran.

I do hope that the firewall (whatever brand is available) on HAL-9000 is
functional, and protecting HAL-9000 (and CATHAINE) from hostile internet
traffic.

Please feel free to post back here if your situation changes.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
Back
Top