Connecting Problem

doekvoet

Well-Known Member
Joined
Jul 24, 2003
Messages
270
Reaction score
0
Location
Cape Town
I have 3 PC's (lets call them A,B & C) at home, all 3 running win2000pro. They are all connected to an older alcatel modem via a hub. Each PC connects to ADSL with its own PPPoE setup and has its own firewall and virus protection.

Since Sunday, PC's A & B log onto ADSL without a problem. However, PC C does not connect. When re-creating the PPPoE accounts, it does show that it can see the ESR1 server, however, when trying to connect I get a "time-out" message. My firewall pops up and tells me it has detected a new network, IP range 169.146.xxx.yyy/255.255.255.0 instead of the normal 165.146.xxx.yyy. Even when I disable the firewall, it still will not connect.

When setting PC B to internet connection sharing, PC C does pick this up and I can use the internet as normal using internet connection sharing.

I have run a full virus scan as well as AD-Aware - no virusses and all addware cleaned out - but still the same problem of can not connect.

Anyone got an idea of what the problem might be or where I can start looking for the problem? I have uninstalled the PPPoE and reinstalled, but this also did not help.
 
to be honest i cant really help you exept tell you what i would do, and that is reload windows. Whenever something messes up big time like in your case with windows, it means reload time! Good luck
 
Please do not reload Windows

It seems that your machine gets a wrong IP address from somewhere, ie it either does not see the correct DHCP server, in the case of a dynamic IP or it has the wrong fixed IP address configured. If the IP address is wrong then 10 to 1 your firewall will reject the messages that it sends. The fact that it works with ICS seems to confirm this, because I believe that the ICS machine would act as the DHCP controller.

I once had a similar problem with a windows 98 machine, which was caused by a wrong winsock DLL. I cannot remember how I fixed it, but I think that on Win2kPRO it may be an idea to remove the whole network setup, ie delete your network card in the System part of control panel. It will then be autodetectedc when you boot up again and reinstall the TCP software. But just in case this does not happen automatically , you should ensure that you have all your network card settings documented. Hope this helps
 
No luck as yet - I have uninstalled and re-installed the network card, the PPPoE client as well as TCP/IP and replaced the network cable - still the same problem.

Anyone with any more ideas as to what may cause the problem?
 
Make sure ICS is removed from all other machines. This could well be where your IP is comming from. 169.xxx.xxx.xxx certainly seems to indicate this at least.
 
u could also try using permanent ips as 2000 sometimes has problems with dhcp
 
try using pc A and pc C without pc B and see if it worx then, it'll jus simplify ur prob and tell u if the pc is at fault or sumthin else.
 
Just spend the money and get a router, that will handle PPPOE connection, and share that between the three machines.
 
Byrd said:
Make sure ICS is removed from all other machines. This could well be where your IP is comming from. 169.xxx.xxx.xxx certainly seems to indicate this at least.

169.xxx.xxx.xxx addresses are assigned by the local machine when it can't get an address from the dhcp server.
 
check that "DHCP Client" is started in your services. If not start it and also ensure that it runs automatically on startup
 
thisgeek said:
169.xxx.xxx.xxx addresses are assigned by the local machine when it can't get an address from the dhcp server.

169.254.XXX.XXX - is APIPA (address assigned by the local machine), doekvoet is getting 169.146.XXX.XXX.
 
Top
Sign up to the MyBroadband newsletter
X