• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

can't ping out?

S

SuperT

Senior member
aloha, we have an NT4.0 proxyserver set up to be DHCP. we can see everyone on the network but have a couple of problems. problem 1 is we can all browse the web but cannot ping out in a command window (to either a domain name or an IP address). problem 2 is our DHCP isn't serving IP's. some of our workstations are Win98 and some Win2k, but if the IP is released from any of them a static one must be entered. do you think these problems are inter-related or no? thanks for ANY advice!😉
 
1) Check to make sure ICMP isnt filtered. If you can reach the net but not ping at all, that may be the problem. Alot of places filter it out on purpose.
2) Is the DHCP server on the same subnet as the DHCP clients? If not, are your routers BOOTP RFC 1542 compliant?
 
You may have to run a scavenge process on the DHCP server to recover old used addresses. Early versions (NT4, f'rinstance) didn't always recover the addresses after they bcame stale.

FWIW

Scott
 
Scott, why does this happen? Most of my DHCP experience is with 2k. Is it that the clients don't release properly, or that the Server doesnt recognize the release? How common is it?
 
hey thanks for the replies. i guess i should ask how i may go about refreshing the DHCP for new IP's to serve. i've not done that before. thanks!
 
also guys, the fact is here too, that the win98 clients don't release the IP's. they are set to obtain automatically but if they are forced to release they cant get back on w/o a static IP entered.
 
Well, it's been a while, but my recollection is that the server will run the scope of addresses, when it gives out the last address, it just stops handing them out until a "scavenge" is done to recover stale/expired addresses. This was a real early effort from Microsoft, so it might have been a "get it out the door, we'll fix it later" kind of thing (we're talking NT4 server here).

I don't belive it's necessarily a client thing, because we used the NT4 servers to pass out addresses and parameters to MS and non MS clients, and the same thing happened in both cases.

I dunno the story on it, but that's the way I remember it (not that my memory is all that reliable either......)

FWIW

Scott

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top