View Full Version : Network Connection
siggy
19th November 2001, 19:09
Ok I dont know if this is hardware or software. But I have never been one to stay OT anyway.
I have finished building my newest addition. (Thank you MechCD, Dustin, and Sniper for all your assistance)
ASUS A7V133-c
Tbird 1.33 with Volcano 5 (OC'd to 1.43)
Win2000
256MG RAM P133
Everything works great, however I can not get a network connection. I have swapped the slot, the card, and the cable. Nothing seems to work. It is getting an IP address but I cannot PING anything. I get "unknown Host" as a response.
I am at my wits end. (I know its a short trip) So if anyone has any ideas on how I can get this idle computer on the network so I can get it crunching. Please post here. :hugz:
pelligrini
19th November 2001, 19:24
I assume you have some sort of DHCP server set up, being that you say it is getting an IP. If it is getting an IP, the slot, card and cable are fine.
If you are running a peer-to-peer LAN on a Microsoft OS, do you have it on the same Workgroup as everything else?
PS nice new system! :)
zhotfire
20th November 2001, 01:05
Siggy, what's the ip that it's getting? If there's no dhcp server present, windows will assign a bizarre "internal" ip, and you won't be connected to anything... are you running some kind of internet connection sharing software on the "server" machine? Are you using a hub/switch or pluggin into a card on the "server" machine?
siggy
20th November 2001, 08:12
Originally posted by pelligrini
I assume you have some sort of DHCP server set up, being that you say it is getting an IP. If it is getting an IP, the slot, card and cable are fine.
If you are running a peer-to-peer LAN on a Microsoft OS, do you have it on the same Workgroup as everything else?
PS nice new system! :)
I have no idea what a peer-to-peer is. Normally I just plug the thing in and it lets me on to the internet.
Ya know it seems the more I learn, the more I realize there is more to learn. :sad:
siggy
20th November 2001, 08:17
Originally posted by zhotfire
Siggy, what's the ip that it's getting? If there's no dhcp server present, windows will assign a bizarre "internal" ip, and you won't be connected to anything... are you running some kind of internet connection sharing software on the "server" machine? Are you using a hub/switch or pluggin into a card on the "server" machine?
The IP is 192.168.0.169
They are plugged into a router.
after that I have no clue as to what you are asking. I am running Win2000 on both machines.
:sad:
verT
20th November 2001, 08:46
Is there a router acces page that you can check? I know with Linksys you can check the status and it will let you know what your external IP address is. Can you ping the other computer via it's IP address?
On the router access page in IE you should see some sort of connection page or tab or button. Is the router statically configured? Is it supposed to be Dynamically configured? If it's statically configured and your ISP sets you up with DHCP there are issues that can arise.
Daniel, Laura, and Nora
20th November 2001, 09:32
I've had good luck with dixie cups and a string in a pinch.
D
siggy
20th November 2001, 11:40
Originally posted by verT
Is there a router acces page that you can check? I know with Linksys you can check the status and it will let you know what your external IP address is. Can you ping the other computer via it's IP address?
On the router access page in IE you should see some sort of connection page or tab or button. Is the router statically configured? Is it supposed to be Dynamically configured? If it's statically configured and your ISP sets you up with DHCP there are issues that can arise.
Dang verT you can really spit out some questions.
1. I dont know if there is a router access page. I do know that the router can receive multiple IP's but the router only sends a single IP to the cable modem, so my cable modem (and provider) only thinks there is one computer.
2. as for pinging the other computer
I went to the cmd screen and typed"/ping 192.168.0.169
and it replied "/ping is not recognized as an internal or external command, operable program or batch file
3.as for the connection page in IE it is set to get an IP automatically
4. on the ipconfig is states that the DHCP is enabled.
<<HUGS>>
siggy
20th November 2001, 11:42
Originally posted by Daniel, Laura, and Nora
I've had good luck with dixie cups and a string in a pinch.
D
Thanks Daniel, and if I could get Stanford to hold the other dixie cup, maybe I could get a gene crunching on that computer :(
pelligrini
20th November 2001, 11:48
What are the other ip's of your other machines on the lan? The new numbers don't seem quite right?
My Linksys router also has a place to specify the number of machines on the lan, if yours can, have you exceeded the specified amount with your new machine?
siggy
20th November 2001, 11:58
Originally posted by pelligrini
What are the other ip's of your other machines on the lan? The new numbers don't seem quite right?
My Linksys router also has a place to specify the number of machines on the lan, if yours can, have you exceeded the specified amount with your new machine?
I only have 2 computers
This computers IP is 192.168.0.166
I dont know if there is any place to specify the number of machines. I have 4 slots on the front of the router, so I just assumed that I could plug 4 in. as a matter of fact I have used this second cable before, on the laptop and I did not have any problems.
pelligrini
20th November 2001, 12:08
I guess the numbers are right. 166=current, probably 167 for laptop, 168 for the first nic, and 169 for the second tried nic. Hmmm... it should be working if you are getting an IP from the DHCP. I'm out of ideas. :(
MikeTimbers
20th November 2001, 12:32
When you do the "ping" command don't precede it with a slash.
Without the quotes type "ping 192.168.0.169"
If you still get the "command not recognised" etc you need to locate the ping command. Then run the same command from that directory.
One other thing:
True story
I recently created a home lan, configured the new machine, configured the original machine, hard-wired IP, simple, eh?
Wouldn't work.
Couldn't ping. Nothing. Deleted the cards, recreated them. Wouldn't work.
Then :rolleyes: turned off ZoneAlarm on main machine.
Wurm
20th November 2001, 13:03
for pingin i use languard gfi.com (http://www.gfi.com/languard/)
i have also been able to seen the some of the routers on the network of my cable provider maybe you could see your router to
anyway its a nice prog and it is able to give you lots of info about your network
verT
20th November 2001, 13:08
Try typing "ping 127.0.0.1"
This is a loopback IP address and will let you know if your TCP/IP protocol is installed properly. If it isn't uninstall it and reinstall it. This should "fix" the problem.
siggy
20th November 2001, 13:17
Originally posted by MikeTimbers
When you do the "ping" command don't precede it with a slash.
Without the quotes type "ping 192.168.0.169"
If you still get the "command not recognised" etc you need to locate the ping command. Then run the same command from that directory.
One other thing:
True story
I recently created a home lan, configured the new machine, configured the original machine, hard-wired IP, simple, eh?
Wouldn't work.
Couldn't ping. Nothing. Deleted the cards, recreated them. Wouldn't work.
Then :rolleyes: turned off ZoneAlarm on main machine.
OK I ping'd the IP and got
Ping statistics for 192.168.0.169:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
siggy
20th November 2001, 13:22
Originally posted by verT
Try typing "ping 127.0.0.1"
This is a loopback IP address and will let you know if your TCP/IP protocol is installed properly. If it isn't uninstall it and reinstall it. This should "fix" the problem.
Here is what I got on both computers.
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms 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
verT
20th November 2001, 13:27
Are you running any firewall software on your computers, Black Ice defender, Zone alarm etc.?
verT
20th November 2001, 13:29
Try a different cable....? A different port on the router....
siggy
20th November 2001, 13:30
Originally posted by verT
Are you running any firewall software on your computers, Black Ice defender, Zone alarm etc.?
I only have Norton AntiVirus, that I'm aware of.
siggy
20th November 2001, 13:31
Originally posted by verT
Try a different cable....? A different port on the router....
I changed the cable, then I changed the Slot, then I changed the NIC card. Also tried all 4 ports on the router. :sad:
verT
20th November 2001, 13:35
Crap I'm running out of ideas......:confused:
Sorry Siggy, I'm at a loss right now. I do some more research and let you know if I come up with anything.
verT
20th November 2001, 13:36
What OS is on the new computer?
siggy
20th November 2001, 13:38
Originally posted by verT
What OS is on the new computer?
<<HUGS>> verT
I have Win2000 on both computers.
verT
20th November 2001, 13:49
the account you log on with is an admin account right? hmmmm
What about updated drivers for the NIC?
siggy
20th November 2001, 14:18
Originally posted by verT
the account you log on with is an admin account right? hmmmm
What about updated drivers for the NIC?
Yes I am loggin on as Admin on both computers.
the nics are both 3com. and they are both using the same drivers.
Dave S
20th November 2001, 14:59
Sig have U turned everything off?
try this....
1 turn everything off
2 turn modem on
3 turn router on
4 turn PC on
let me know?
Bruce
20th November 2001, 15:33
You've had lots of good suggestions, but so far, no luck.
From what I understand, you have two windows computers plus a router - which makes 3 devices on a LAN that all should be able to
talk to each other.
I don't see a brand name for your router, but my comments probably apply to any router.
You said you did a ping but got 100% packet loss. That is a big clue. So far nothing has been said that explains it.
Does your router have lights that show speed and/or data? Do the lights on your ethernet cards look right? IIRC, you have two lights on each card -- one for speed, and one for data. Everything must be at the same speed (exception: The modem line can be at 10 with everything else at 100) -- and you should be able to see data during a ping.
1) Each of the computers should always be able to ping 127.0.0.1 and get the same number of packets received as transmitted -- i.e. 0% loss. (When you say you can ping an address, that always means with 0% loss -- or certainly not 100% loss -- sometimes you may loose the first packet.)
2) Each of the computers should have a different ip address within the same general range of addresses. (Lots of details omitted here, but let's just say you don't need to know it for now.) 192.168.0.169 is one of the appropriate addresses. Write down both (all of the) addresses. Each should be able to ping itself and should be able to ping all of its neighbors. Apparently part of this fails. We need to focus on what that is and why. Once that part is figured out, you probably won't need to go to the next step. Post what works and what doesn't.
3) Everything I've said actually applies to the router too, except that it doesn't have a keyboard and monitor, so it is harder to explain. There are lots of settings in the router which might or might not need work. You usually can log on to it (perhaps with a browser -- and always with telnet). That's tough, though, if you don't know its ip address. Sometimes there is also a DS9 connector to plug in an old dumb terminal, but you won't have one of those just laying around. If all else fails, they generally have a button that resets everything to factory defaults -- and then you consult the manual for what the settings are. Don't try that yet.
4) You actually have a combination hub - router. The hub part allows you to connect your computers as a LAN whether or not you have an external connection. The router / firewall part picks off messages intended for the internet and (after some translation) sends them to your modem -- and reverses that process for incoming messages. Looking just at the hub part: Identify the modem port -- because it is unique. The remaining ports are probably identical, but sometimes there is one special port called an uplink port. If you have one of those, avoid it for now.
5) Somebody mentioned DHCP. It could be that we've got multiple DHCP hosts. Both win2k and the router might be doing this. (all three?) If somebody with Win2K can walk her through checking that part, it might help.
siggy
20th November 2001, 15:48
Originally posted by Dave S
Sig have U turned everything off?
try this....
1 turn everything off
2 turn modem on
3 turn router on
4 turn PC on
let me know?
Well some interesting things happened Dave. One thing I found out is that I was not logged on as Admin on PC#1. Secondly I have forgotten my password for my user :sad: :sad: now all my desktop icons are gone:sad: :sad:
Im going to go cry now.
verT
20th November 2001, 15:59
log in as admin go to START>Programs>Administration Tools>Computer Management
click on Local Users and Groups click the Users folder right click on your account and click password.
That one I know how to fix :)
Provided you know the admin password......
siggy
20th November 2001, 16:04
Originally posted by verT
log in as admin go to START>Programs>Administration Tools>Computer Management
click on Local Users and Groups click the Users folder right click on your account and click password.
That one I know how to fix :)
Provided you know the admin password......
Thank you very much I owe you about 1000 hugs. :hugz:
siggy
20th November 2001, 16:10
Originally posted by Bruce
You've had lots of good suggestions, but so far, no luck.
SNIP....
Ok the router is a D-Link DI-704.
Here are the results of the pings.
PC#1(192.168.0.166)
Ping to 127.0.0.1 ping was good
Ping to 192.168.0.166 ping was good
Ping to 192.168.0.169 ping was good
PC#2(192.168.0.169)
Ping to 127.0.0.1 ping was good
Ping to 192.168.0.166 Ping was BAD 100% packet loss
Ping to 192.168.0.169 ping was good
As for the lights I only have one light on the NIC cards and they're on. As for the router, I saw the flashing lights while doing the ping test.
verT
20th November 2001, 16:20
PC #2 is the new one right?
If this is the case it seems like PC #1 has some sort of firewall protection.
Can you ping the router? I'll guess the IP address is 192.168.0.1
MechCD
20th November 2001, 17:14
Originally posted by siggy
Dang verT you can really spit out some questions.
1. I dont know if there is a router access page. I do know that the router can receive multiple IP's but the router only sends a single IP to the cable modem, so my cable modem (and provider) only thinks there is one computer.
2. as for pinging the other computer
I went to the cmd screen and typed"/ping 192.168.0.169
and it replied "/ping is not recognized as an internal or external command, operable program or batch file
3.as for the connection page in IE it is set to get an IP automatically
4. on the ipconfig is states that the DHCP is enabled.
<<HUGS>>
Somethin ain't right there.......
I just tried it.
Start > Run
typed in"CMD"
types in "ping 192.168.0.2" and ping erked. Maybe its the slash in front of it? try it without a slash
MechCD
20th November 2001, 17:20
Originally posted by siggy
Ok the router is a D-Link DI-704.
Here are the results of the pings.
PC#1(192.168.0.166)
Ping to 127.0.0.1 ping was good
Ping to 192.168.0.166 ping was good
Ping to 192.168.0.169 ping was good
PC#2(192.168.0.169)
Ping to 127.0.0.1 ping was good
Ping to 192.168.0.166 Ping was BAD 100% packet loss
Ping to 192.168.0.169 ping was good
As for the lights I only have one light on the NIC cards and they're on. As for the router, I saw the flashing lights while doing the ping test.
I remember this somewhere, i had the same prob.....
in the sharing tab... somewhere..... set access to allow "users" full access........ or it may have somethin to do with the user list... i'm not sure which
I think i'm confused. the IP endin with 166 is PC #2 right?
Bruce
20th November 2001, 17:27
Originally posted by verT
PC #2 is the new one right?
If this is the case it seems like PC #1 has some sort of firewall protection.
Can you ping the router? I'll guess the IP address is 192.168.0.1
You're obviously getting to the internet. Which PC is working through the router?
Right, verT, 192.168.0.1 should be the default address for the router.
Can you ping it from both of the computers?
If so, check that it is configured as a gateway in the configuration screen where TCPiP is bound to the NIC. Actually, one thing to check is that all of the TCPIP settings are the same (since you have "obtain IP address automatically set -- otherwise the assigned addresses must be different, but we know that's already correct.)
phil
20th November 2001, 17:45
OK the D-Link has a default IP address of 192.168.0.1. Try Pinging it from both machines...if you get a reply, then we are on the right track.
Now, to do some Router config. Open a browser and in the address bar type: http://192.168.0.1
A screen will pop up asking for your password. Type in "admin" and click login. At the bottom of the screen, click on the "tools" link and change the default password (admin) to something else.
Now click the "setup" link. In the LAN IP address input 192.168.0.1
WAN type should normally be "Dynamic IP address". If you have to change this, then you will be asked for a hostname which is optional. Enable "renew IP forever"
Now click the "DHCP" link and disable DHCP. Now log out of the router by pressing the "log out" button :rolleyes:
Pick a machine and go to the network properties:
Start > Settings > Network and Dial up > Local Area Connection. Click Internet Protocol (TCP/IP) and then the properties button. Now click the "use the following IP address" button. Fill the boxes in as follows:
IP Address: 192.168.0.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
Preferred DNS Server 192.168.0.1
Click OK and OK again to accept the details.
Do the same for the second machine, using the same details except the IP Address which you should use 192.168.0.3. Now re-boot both machines. You should now be able to access the Internet from both machines and also ping both machines using the above IP addresses. If not, let me know.
I never use DHCP as I prefer to set my IP addresses manually.
Bruce
20th November 2001, 18:31
Originally posted by phil
I never use DHCP as I prefer to set my IP addresses manually.
Me too, though I leave a few DHCP addresses for when somebody drops by with a laptop or something.
siggy
20th November 2001, 20:29
Originally posted by verT
PC #2 is the new one right?
If this is the case it seems like PC #1 has some sort of firewall protection.
Can you ping the router? I'll guess the IP address is 192.168.0.1
Yes PC#2 is the new one.
PC#1 does not have a firewall that Im aware of. Unless Norton AntiVirus is a firewall.
I have taken the router out of the loop trying to trouble shoot but when I put it back in the loop I will try and ping it.
siggy
20th November 2001, 20:31
Originally posted by Bruce
You're obviously getting to the internet. Which PC is working through the router?
Right, verT, 192.168.0.1 should be the default address for the router.
Can you ping it from both of the computers?
If so, check that it is configured as a gateway in the configuration screen where TCPiP is bound to the NIC. Actually, one thing to check is that all of the TCPIP settings are the same (since you have "obtain IP address automatically set -- otherwise the assigned addresses must be different, but we know that's already correct.)
PC#1 is the one with access to the internet, which was thru the router. However after much work, it is now on the network without the router. I am going to try and put everything back together. But as far as the obtain IP auto, PC1 and PC2 were both set that way.
siggy
20th November 2001, 20:40
Thanks Phil. I printed your out. Im going to try and put the router back in the loop and see if I can get back on the network.
FYI..I took computer #2 off of the router and put it straight into the cable modem. then I called the tech support for my @home service and we tested the hell out of it. I could ping the IP but I could not PING the gateway. Then we released the IPconfig and then tried to renew the IPconfig and got nothing.
1. it is not the cable modem
2. it is not the cable
3. it is not the NIC card.
I dont think it is the drive because the Drives for PC1 and PC2 are the same.
I am about to go insane over this. I have nothing on the PC#2, and am willing to format the drive and start over if anyone thinks that will help. I also checked device manager and there are no conflicts.
So some one let me know if I should wipe the slate clean and start over.
If yes, then I have one question. When I installed Win2000 it wanted to know if the partition should be NTFS or FAT. Which should it be?
<<HUGS>> for everyones help. :hugz: :hugz:
siggy
20th November 2001, 20:51
OK router is back in the loop with PC#1 and it can ping the router.
So far so good.
siggy
20th November 2001, 20:56
Originally posted by phil
OK the D-Link has a default IP address of 192.168.0.1. Try Pinging it from both machines...if you get a reply, then we are on the right track.
SNIP....
Phil, I have a static IP from my ISP. Dont I want to leave it that way?
The problems I have had in the past with the cable modem have been linked to them not see the IP address that is assigned.
Help me understand this :hugz:
wbierman
20th November 2001, 21:09
You may access the Linksys router by typing in http://192.168.1.1 in your favorite browser address bar.
When prompted for Username and password...ignore the user and leave it blank ahd type in "admin" without quotes. Hit the enter key and you will see the main setup window.
I think you need to "point " your new PC at the router. This is done through this sequence...
<start> <Settings> <NetWork and Dial-up Settings> then right-click on the icon... "Local Area Connection"... from the drop down list select "Properties" and click on it... select "Internet Protocol TCP/IP". Click on the Internet Protocol and highlight it. Then click on the Properties Tab just below it. Now you will see the General Tab of the Internet Protocols (TCP/IP) Properties. Select the Advanced button at the bottom of the window.
Look for Default Gateways and click on the Add buttom. Now just enter the LAN (local area netwwork) address of your router...usually 192.168.1.1
You have just set up a "gateway" which is the default IP address of your Linksys router and should be 192.168.1.1 or 192.168.0.1
Just make sure your new PC has a different IP address from all the others.
MechCD
20th November 2001, 21:13
Try swappin NIC cards..... Trya different brand. that just [popped in me head.
I have 2 puters in which 2 very certain nic cards just won't work right. I swapped em and they both work perfectly.
one is a Intel EtherExpress PRO10+ ISA and the other is an old compaq ISA 10baseT.
its hard to explain, but i had a similar problem, i could ping everywhere form the "bad" puter" but only one other puter could see the "bad" puter
phil
21st November 2001, 05:42
Originally posted by siggy
Phil, I have a static IP from my ISP. Dont I want to leave it that way?
The problems I have had in the past with the cable modem have been linked to them not see the IP address that is assigned.
Help me understand this :hugz:
If you have static addressing, leave it as static....the majority of cable modem services use dynamic. Obviously @Home is the exception.
Will, Siggy is using a D-Link router
siggy
21st November 2001, 07:59
Originally posted by phil
If you have static addressing, leave it as static....the majority of cable modem services use dynamic. Obviously @Home is the exception.
Will, Siggy is using a D-Link router
OK thanks Phil. I have PC#2 back in the loop. However it cannot ping the router, nor can it ping its own IP. This is really starting to sound like a software issue. All of the hardware has been swapped out. :sad: :sad:
phil
21st November 2001, 08:20
Sounds like a dodgy NIC....I had one that could send, but wouldn't receive data :rolleyes:
siggy
21st November 2001, 08:24
Originally posted by phil
Sounds like a dodgy NIC....I had one that could send, but wouldn't receive data :rolleyes:
I have swapped the NIC cards. It did not make a difference. :sad:
MechCD
21st November 2001, 10:04
I hate to tell ya this, but you might need to try another brand of card in that puter. Sometim,es its just like that. it doesn't mean that card is "bad", it just doesn't work right with that hardware. You could prolly keep that card and use it in another puter or sell it etc
What motherboards do these puters have?
Martyn
21st November 2001, 13:50
Originally posted by siggy
Yes PC#2 is the new one.
PC#1 does not have a firewall that Im aware of. Unless Norton AntiVirus is a firewall.
If Norton AV is part of Norton internet utilities, they yes, there is a firewall in there as well (good one too) - AtGuard. If it's just a stand alone copy of NAV, then no it isn't a firewall.
siggy
21st November 2001, 20:40
Siggys network problem is all fixed.
I took the computer to Sniper and he fixed it. Took less than an hour. He will not tell me what he did. He just keeps saying "I am the Master"
So thank you everyone for helping me troubleshoot the computer.
<<HUGS>>:hugz: :hugz:
verT
21st November 2001, 20:45
That's usually the way it goes Siggy....:rolleyes:
vBulletin® v3.7.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.