Uninstall DHCP under Win95
Kevin J Barnes
Somehow I have set up DHCP client on Win95 where there is no
domain server. I keep getting Unable to find DHCP .... when I
start up each time, and every several minutes afterwards.
How Can I disable this client?
Thanks much,
Kevin
Gordon McAndrew
Kevin J Barnes <kba...@airmail.net> wrote:
;>Somehow I have set up DHCP client on Win95 where there is no
;>domain server. I keep getting Unable to find DHCP .... when I
;>start up each time, and every several minutes afterwards.
;>How Can I disable this client?
In Control Panel | Network |||| you have to either assign an IP address to
your LAN card (TCP/IP | Properties | IP) or unbind TCP/IP from your LAN
card.
If you want a better answer you will have to post more details of your
computers configuration. ie. LAN, DUN. etc..
Gordon McAndrew
LAN Manager,
Alberta Environmental Centre,
Vegreville,
Alberta, Canada
gmca...@aec.env.gov.ab.ca Home
gor...@aec.env.gov.ab.ca Office
Kevin J Barnes
I need the TCP/IP address for a local inhouse lan, I just do not want
dhcp resolution.
It keeps prompting me and I have said 'YES' show me futher notices, but
maybe if I just say
'NO <g>' it will work. I am concerned about performance if the DHCP
client is constantly looking
for a domain.
Thanks,
Kevin
Joe Morris
Kevin J Barnes <kba...@airmail.net> writes:
>Gordon McAndrew wrote:
>
>> Kevin J Barnes <kba...@airmail.net> wrote:
>> ;>Somehow I have set up DHCP client on Win95 where there is no
>> ;>domain server. I keep getting Unable to find DHCP .... when I
>> ;>start up each time, and every several minutes afterwards.
>> ;>How Can I disable this client?
>> In Control Panel | Network |||| you have to either assign an IP address to
>> your LAN card (TCP/IP | Properties | IP) or unbind TCP/IP from your LAN
>> card.
>I need the TCP/IP address for a local inhouse lan, I just do not want
>dhcp resolution.
I think you're missing something here. Either:
(a) You need to use DHCP in order to set the IP address for your
local inhouse LAN, or
(b) You need to explicitly set an address in the TCP/IP protocol
configuration in the Network control panel, and so do not need
to have DHCP invoked.
The answer is apparently *not* (a) because you state that you want to
disable the DHCP interface in your machine.
If the answer is (b) then you need to contact your network administrator
and find out what address is assigned to you, then configure your TCP/IP
stack using that address. If you don't do this, DHCP will be used in an
attempt to find a usable IP address when you boot your system.
There is no way to directly "disable" the DHCP client; it will be invoked
whenever you have the Microsoft TCP/IP protocol loaded, and that protocol
is bound to an active network connection, *and* either:
(a) The IP address configuration dialog for an instance of the TCP/IP
protocol bound to an active network adapter has the "Obtain an IP
Address Automatically" box checked, or
(b) The "Specify an IP Address" box is checked, but the IP address
specified is 0.0.0.0 .
DHCP is "disabled" if any of these conditions are not met.
(Note: obtaining an IP address for a dialup PPP connection is a completely
different issue.)
Joe Morris / MITRE
Narayan Behera
This was a very well explained mail, and answered some
similar questions I had. There are some more!
I ran into the DHCP problem when I was setting up my Win95
PC for a LAN( with just one other machine, an SGI Indy Unix box).
Win95 kept complaining "unable to obtain IP address from a DHCP
server". I had no clue what DHCP was. First I wrongly remembered it
as DHCF, and found from a Net Search that it stands for Distributed
Host Command Facility:)
My PC still does not work on the LAN. It says "Unable to browse the
network; Network is inaccessible" when I click the Entire-Network
icon inside NetwokNeighborhood. Any idea why?
I have the "Specify an IP address" box checked against the TCP/IP
adapter properties. The address is 1.1.1.2, so DHCP is not invoked.
The client is the "Client for NetWare Networks", and DNS is currently
disabled on the DNS configuration panel of TCP/IP properties.
I think the Indy side of the network is working. I tried it with
the /usr/etc/ping command with the PC machine name as argument, and
I see the packets are going back and forth.
Thanks much.
Sincerely,
Narayan Behera
--
_______________________________________________________
Narayan Behera Numeritec Corporation
voice: (603) 448-3499 42 Wolf Road, Suite 312
Fax: (603) 448-0070 Lebanon, NH 03766
e-mail: nar...@numeritec.com
www: http://www.numeritec.com
_______________________________________________________
Jaime Metcher
Why are you using the Netware client? Is the Indy running Netware????
Anyway, the Win95 network browser is a NetBEUI thing, as I understand
it - neither TCP/IP or IPX/SPX have anything to do with it..
--
Jaime Metcher
Systems Programmer (i.e. plugger-in of printers and replacer of toner)
University of Queensland, Australia.
Joe Morris
Narayan Behera <nume...@cyberportal.net> writes:
>I ran into the DHCP problem when I was setting up my Win95
>PC for a LAN( with just one other machine, an SGI Indy Unix box).
>My PC still does not work on the LAN. It says "Unable to browse the
>network; Network is inaccessible" when I click the Entire-Network
>icon inside NetwokNeighborhood. Any idea why?
>I have the "Specify an IP address" box checked against the TCP/IP
>adapter properties. The address is 1.1.1.2, so DHCP is not invoked.
>The client is the "Client for NetWare Networks", and DNS is currently
>disabled on the DNS configuration panel of TCP/IP properties.
>I think the Indy side of the network is working. I tried it with
>the /usr/etc/ping command with the PC machine name as argument, and
>I see the packets are going back and forth.
Something's rotten here.
You've got two boxes that are the only nodes on the net, but your
WIN95 machine is using Client for Netware Networks. Where is the
NetWare server?
You don't have the Client for Microsoft Networks loaded. Even if
you did, where is a node that is willing to talk to the MS Netowork
client on your WIN95 system?
So...if you've not got a NetWare server on the net, and there's
no other system that is talking Microsoft Networking, what do you
expect the "browse network" function to display?
Joe Morris / MITRE
Joe Morris
Jaime Metcher <met...@spider.herston.uq.edu.au> writes:
>Why are you using the Netware client? Is the Indy running Netware????
>Anyway, the Win95 network browser is a NetBEUI thing, as I understand
>it - neither TCP/IP or IPX/SPX have anything to do with it..
No. I assure you that NetBEUI is *not* necessary for browsing; that's
a good thing because by policy we do not permit that obnoxious protocol
to be used on our network backbone. (NetBEUI can be used to good
advantage on trivial networks but it's an unmitigated disaster on
large nets because it's unroutable.)
Perhaps you've confused NetBEUI with NetBIOS? If so you aren't the
first; the names are so similar that it's a common mistake.
Browsing information (using NetBIOS) can be carried on NetBEUI,
TCP/IP, or IPX. You can demonstrate this easily if you've got access
to a net that supports PPP: configure a system with only TCP/IP
in its PPP client interface and dial into the net: browsing will
work properly (or should, assuming that you've sacrificed the proper
number of chickens in the past week).
Joe Morris
Michael Thielker
Hi,
you are confusing something here: you cannot browse to a unix box, no
matter what you do. TCP/IP only machines do not show in the network
neighborhood at all. I run about 10 unix boxes, not a single one shows,
and that's perfectly alright. With the client for NetWare and either
TCP/IP or NetBEUI you can see NetWare servers and Win95 machines. If you
also load the MS client you can see NT servers and workstations as well.
No unix box will ever show there.
Mike
>> I ran into the DHCP problem when I was setting up my Win95
>> PC for a LAN( with just one other machine, an SGI Indy Unix box).
>> Win95 kept complaining "unable to obtain IP address from a DHCP
>> server". I had no clue what DHCP was. First I wrongly remembered it
>> as DHCF, and found from a Net Search that it stands for Distributed
>> Host Command Facility:)
>>