If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
2 PCs see each other but one can't go online
Hello!
I am trying to set up a network installation with a linksys DSL router (BEFSR41 v3). Two machines running Windows ME are connected to the router. I am using static IPs. Both PCs can ping each other and see each other. Both can ping the router successfully but only one of them opens websites. The other one can't connect to the internet through the router. Ping yahoo.com results in timeout. The other PC works fine (pinging the web, opening websites). I checked TCP/IP settings and except for the different local IP erveything is identical - gateway, DNS... What else could cause PC2 to fail when trying to ping into the internet? I already cleaned network settings and re-installed all protocols and network adapters to prevent problems with the Windows ME network socket/stack. Thanks for help! Bye Oliver |
#2
|
|||
|
|||
In article , Oliver Breitfelder says...
I am trying to set up a network installation with a linksys DSL router (BEFSR41 v3). Two machines running Windows ME are connected to the router. I am using static IPs. Both PCs can ping each other and see each other. Both can ping the router successfully but only one of them opens websites. The other one can't connect to the internet through the router. Ping yahoo.com results in timeout. The other PC works fine (pinging the web, opening websites). I checked TCP/IP settings and except for the different local IP erveything is identical - gateway, DNS... What else could cause PC2 to fail when trying to ping into the internet? I already cleaned network settings and re-installed all protocols and network adapters to prevent problems with the Windows ME network socket/stack. The only things that come to mind for the failing computer are a misconfigured software firewall, or a hosts file with bad entries. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#3
|
|||
|
|||
"N. Miller" schrieb im Newsbeitrag
om... In article , Oliver Breitfelder says... The only things that come to mind for the failing computer are a misconfigured software firewall, or a hosts file with bad entries. Hosts file sounds interesting and possible. I'm gonna check that out. Thanks! Bye Oliver |
#4
|
|||
|
|||
In article , Oliver Breitfelder says...
"N. Miller" schrieb im Newsbeitrag om... In article , Oliver Breitfelder says... The only things that come to mind for the failing computer are a misconfigured software firewall, or a hosts file with bad entries. Hosts file sounds interesting and possible. I'm gonna check that out. Thanks! If your computer ever harbored hijackware, some of that kind of malware is known to modify, or create a hosts file which blocks access to certain "good guy" sites. The hosts file does not exist in a default installation; it is a throwback to a time before the DNS system was set up. It holds the key to converting a Fully Qualified Domain Name (FQDN) to an IP address. Most people today create one to redirect HTTP requests to the "localhost". If there is a hosts file, the first "active" line should be: 127.0.0.1 localhost There should be a "hosts.sam" file which includes some rudimentary instructions, including the spacing. I think at least two are necessary; but I usually use four, or so, for legibility. I include a couple of entries for my router, and such, so I don't have to remember the IP address. An example: 192.168.102.1 Chihiro With that entry, I just type "Chihiro" in my browser URL bar, and I go straight to my router configuration pages. Beyond that, I have "blocking" aliases for sites I do not wish my browser to access. An example: 127.0.0.1 doubleclick.com Wildcards won't work. Nor can you alias one IP address to another; the purpose is to create a one-to-one table of FQDNs to IP addresses. So you have to have separate entries for undesirable sites, if more than one FQDN exists. An example 127.0.0.1 doubleclick.com 127.0.0.1 doubleclick.net So all you need to do is first see if you even have a hosts file, then open it to check the content. Notepad will work if the file is under 40k, or so; anything over that size and you should use Wordpad. Any text editor will do the job, though. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#6
|
|||
|
|||
On Sun, 8 May 2005 18:16:51 -0700, Vicki wrote:
"Oliver Breitfelder" wrote in message ... Hello! I am trying to set up a network installation with a linksys DSL router (BEFSR41 v3). Two machines running Windows ME are connected to the router. I am using static IPs. Both PCs can ping each other and see each other. Both can ping the router successfully but only one of them opens websites. The other one can't connect to the internet through the router. Ping yahoo.com results in timeout. The other PC works fine (pinging the web, opening websites). I checked TCP/IP settings and except for the different local IP erveything is identical - gateway, DNS... What else could cause PC2 to fail when trying to ping into the internet? I already cleaned network settings and re-installed all protocols and network adapters to prevent problems with the Windows ME network socket/stack. Thanks for help! Bye Oliver Are the two computers using private addresses? a 192.168.1.xx or 10.0.0.xx address? What address is your router set to? Usually the router is set up and then the two inside computers are set up to automatically get an ip address using dhcp. So not using static ip addresses. Does this help you? Maybe; if he is still looking for responses one month after posting. Oh, and the private IP addresses, as defined in RFC 1918 a 10.0.0.0/8; using the popular "X" notation: 10.xx.xx.xx 172.16.0.0/12; using the popular "X" notation: 172.16.xx.xx 192.168.0.0/16; using the popular "X" notation: 192.168.xx.xx I don't use anything in 10.0.0.0/8, but I do use both 172.16.0.0/12 (I have 172.29.61.1 as a gateway), and 192.168.0.0/16 (I have 192.168.102.1 as a gateway). -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
#7
|
|||
|
|||
"N. Miller" schrieb im Newsbeitrag
.. . [..] Maybe; if he is still looking for responses one month after posting. Oh, and the private IP addresses, as defined in RFC 1918 a 10.0.0.0/8; using the popular "X" notation: 10.xx.xx.xx 172.16.0.0/12; using the popular "X" notation: 172.16.xx.xx 192.168.0.0/16; using the popular "X" notation: 192.168.xx.xx I don't use anything in 10.0.0.0/8, but I do use both 172.16.0.0/12 (I have 172.29.61.1 as a gateway), and 192.168.0.0/16 (I have 192.168.102.1 as a gateway). I found a solution. First i used 192.168.0.254 as router IP and 192.168.0.1 and .2 as client IPs. That was a problem! The linksys router did not work with any other IP address than the one it was configured with on the date of delivery. When i reconfigured the router to 192.168.1.1 (factory setting) and .2 & .3 for the clients everything works perfectly. Just as i thought, all settings on the clients were correct. Don't know what causes this strange behaviour of the linksys device but it's rather irritating. Thanks for your help. Bye Oli |
#8
|
|||
|
|||
On Thu, 12 May 2005 09:49:17 +0200, Oliver Breitfelder wrote:
I found a solution. First i used 192.168.0.254 as router IP and 192.168.0.1 and .2 as client IPs. That was a problem! The linksys router did not work with any other IP address than the one it was configured with on the date of delivery. When i reconfigured the router to 192.168.1.1 (factory setting) and .2 & .3 for the clients everything works perfectly. Just as i thought, all settings on the clients were correct. Don't know what causes this strange behaviour of the linksys device but it's rather irritating. I find it odd that a Linksys router would not work with any network address it was configured to use. I have a Linksys BEFSR11. I have configured it for about three other network addresses than the default, and it has worked for each network address. Most recently, I had it set with 192.168.102.2 on the WAN port, and 192.168.3.2 on the LAN port. It worked as configured. -- Norman ~Win dain a lotica, En vai tu ri, Si lo ta ~Fin dein a loluca, En dragu a sei lain ~Vi fa-ru les shutai am, En riga-lint |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Ping: Gary Terhune W98SE online security | ms | General | 10 | December 31st 04 01:14 AM |
Money99 + Spybot -- unable to get online quotes now | lili marlene | Software & Applications | 0 | October 10th 04 05:16 AM |
Inability to access Microsoft Online Assisted Support | Ellis Butler | General | 0 | August 13th 04 09:51 PM |
No sound when online | Dawn | Multimedia | 0 | June 13th 04 05:46 PM |
My system reboots while online... | rdbr | Internet | 0 | June 5th 04 05:09 AM |