Hi all the Experts,

I have a DCHP Windows 2000 server with 2 NIC... one is connected to the DSL modem, the 2nd one is connected to the HUB. Of course I have a Verizon online DSL with A Dynamic IP address and share it with 3 windows 98 clients via a HUB. My problem is my DHCP server assign an Automatic Private IP Addressing (APIPA) wich is 169.254.x.x all the time several weeks ago. And my clients PC can no longer surf the internet because of the DHCP can not assign the ip address anymore.
I want to know if someone can help me out to solve this problem. The NIC that is connect to the HUB ip address is:192.168.0.1
and the NIC that is connect to the DSL modem , I have to use (Obtain an IP Address Automatically) to be able to surf the internet on the server itself. If I enter a static ip address (192.168.0.25) it won't work anymore.
So, please really need help to configure the ip address that work between my DSL modem, my HUB and the 2 Network cards..! And to share my DSL speed with those 3 windows 98 clients again..!

Thanks
Rithy69

rithy89, hi, I am a little confused with your setup. Please explain again your complete computer setup. Do you mean to say you have the hub connected to the DSL modem, and the hub has 4 ports or more? Is your 2nd PC and your other 3 client PCs connected to 1 hub?
Without knowing your complete pc-dsl-hub setup, it is difficult to troubleshoot your network.

By the way, the 169.254.x.x is anumber assigned by your DHCP when it can't find a router, for example, whicj means your internet connection is not going to work. Instead, your DSL modem should be assigned 192.168.0.1 assigned the 198.168.0.1, or more precisely, a router, for example.

I recommend getting a router with at least 4 ports if you can afford it. The problem lies in your hub, which is not very good for sharing the internet connection on a network without first using a router, a bridge, or a switch, because it can't assigned number from your DHCP, that a router can. A hub is not very "smart" by itself, unless you are getting a hub called "intelligent hub". All a hub does is relay signals from a router, bridge, or switch. A hub does not enable dedicated line like switch, does not reduce traffic like a bridge, and certainly does not and can not store and remember "routing numbers" like a router.

That is why I recommend a router which will automatically, through your DHCP, assigned the proper private IP addresses of 198.168.0.1, 198.168.0.2, and so on. The best router brand is LINKSYS or NETGEAR.

Elina,

Here is my network setup:
A DCHP Windows 2000 server has 2 Network cards, one is connected to the DSL modem and the other one is connected to the 8 ports HUB. From the HUB I connected 3 windows 98 clients.
You are right, I might need to invest in a router... but it used to work fine whithout a router...

Thanks again for your help
Rithy69 :) :)

Rithy69, hi again, and thanks for describing to me your detailed network setup. And from the way you've described to me, you sound like you you know your stuff. The hub does work, as you have mentioned all your computers at one time connected to the Internet. But they all connected only because you assigned each one of them a private IP address, right? If you would still like to use your hub and keep your current network setup, I suggests unpluggin everything, starting with the DSL modem, then your WIN 2000,

If I may offer some more advice, I suggests you remove the NIC card that the hub is attached to, and substitute the hub with at least a 5-port router for all your computers.

Sorry, I accidentally, hit the <ENTER> button.

... starting with your WIN 2000 and then the rest of your WIN 98 computers. Wait oh.. say, 5 to 10 minutes to see if the IP addresses will re-set itself. And then re-plug everything back in starting with the modem again.

Now, with the router you likely know that it will automatically assign each PC an IP address, so you don't have to do it manually. Of course, just check on each PC under TCP/IP "OBTAIN IP and DNS automatically".

I have 7 computers on my network, with WIN 2000 server as the main one, like yours. And I used to first set up my network with a hub, too. But because I always had problems with each IP lease number expiring so many times, I got sick of it, and went with a good router, instead. So, that's what I recommend getting a router, and that's what routers are good for anyway--to have IP numbers automatically assigned and automatically remember those IP addresses. :) ;)

Elina,

I'm thinking of replacing my DHCP win2k advance server with a windows 2003 server and buying a linksys BEFSR41 EtherFast Cable/DSL Router with 4-Port 10/100 Switch.
No, I did not assign an ip address manually before. My DHCP server assign automatically an ip address to each client. My server config: 1st NIC card connect to the HUB has this private ip address: 192.168.0.1 no gateway (inside network)... 2nd NIC card connect to the DSL modem used to have this private address: 192.168.0.25 with 192.168.0.1 as a gateway... and the DSL winpoet connection has its ip address 141.156.x.x assign by my ISP (verizon with Dynamic IP) .

Thanks again for your advice

>>192.168.0.25 with 192.168.0.1 as a gateway... and the DSL winpoet connection has its ip address 141.156.x.x

It sounds like the DSL modem was a router that also did NAT (Network Address Translation) and maybe Verizon pushed an "upgrade" to it. The modem may also be a DHCP server.

I'd contact Verizon and see if that modem supports NAT. Or replace it with a DSL modem/router that supports NAT.

I'm having problems with the DHCP Server on Windows 2000 Server Platform. The DHCP server all of a sudden stops assigning IPs to the clients. The server has one NIC with static IP address on the same IP subnet for the rest of the network. The server also has WINS service running.

I have disabled the DHCP Client from the services of the server and sometimes it get started on a reboot automatically despite of the fact that it was disabled from services.

The DHCP Client service should be started in the first place or not, I believe not because the DHCP server is already running as a service.

Also I'm facing problem that whenever I reboot the server it takes hell of a time on Preparing Network Connections.

I need an urgent help to identify and fix the problems, thanks in advance for your prompt response.

Rithy, you did not mention your dsl router model... but you need to make sure it is in "bridged mode". Traditionally, DSL router are run PPPoE, DHCP, NAT, firewalled, etc. If your DSL modem is NOT set in bridged, you have 2 routers back to back.

If you choose not to up grade to the now common broadband routers, consider running your 2k server as a proxy.

Also, if to rid the 169.254. You first need to check for windows socket problem (enter "ftp localhost" at the DOS/Command-line window, you do NOT want the ftp output to have the word "socket"... enter "quit" to exit ftp). If you have socket error you will need to reinstall your tcp/ip stack.

If no socket problem... remove all cables to your dsl modem / powerdown the dsl modem, router, dhcp server and problem PC(s) / wait 2 minutes & reconnect the dsl cables / powerup the dsl modem and WAIT for your "sync" light / if applicable, surf into the modem and verify connectivity and set the modem in "bridged mode" / power up dhcp server - verify connectivity / power up router - verifiy "internet or wan" led is lite / powerup your PC(s).

Although "technically" 169.254 is not a problem, in the broadband world "169.254" is a killer problem common (aka show-stopper). I have heard of people reformatting their drives and reloading the OS - to no avail! Sounds hard to believe to the more I research the problem, the more I suspect a specific trojan or virus as the cause or an inherent windows socket issue.

Good Luck

P2E

Quote:

---

Originally Posted by Rithy69

Elina,

Here is my network setup:
A DCHP Windows 2000 server has 2 Network cards, one is connected to the DSL modem and the other one is conected to the 8 ports HUB. From the HUB I connected 3 windows 98 clients.
You are right, I might need to invest in a router...but it used to work fine whithout a router....

Thanks again for your help
Rithy69 :) :)

---