> -----Original Message-----
> > So then, what should I do from there? That's exactly what I did
> > (except the /release /renew part) in the first place, but when I
> > statically assigned myself that IP in Linux by writing it to
> > /etc/network/interfaces, I had the problem.
>
>
> The "ipconfig" command by itself just reports what Windows
> believes is
> its current IP address. The /release tells Windows to tell the DHCP
> server that it no longer wants this address and the server
> can have it
> back to reallocate to whatever client needs one. The /renew tells
> Windows to ask the DHCP server for an address, and in many cases will
> result in the same IP being given back to the client.
>
> If the /renew doesn't work, there's something else at work on your
> network, such as a network switch getting confused (we had
> some similar
> problems a few years ago on our new ATM network). Generally,
> waiting 15
> minutes or so allowed the "glitch" to clear up out of the network
> hardware. (Or alternatively we could move to a different network port
> and get going again.)
Well, I was in Linux again today and I did a couple of things. Here is what I did and
the response I got, can anyone comment on this?
1) I installed "pump" upon the recommendation of a co-worker (using "apt-get install
pump", from the CD-ROM). But executing "pump -i eth0 --status" yields the error
message "Operation failed". So I must need to configure it or something.
2) I changed the /etc/network/interfaces file to say
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
(without the indent) But then when I executed "/etc/init.d/networking restart", it
just hung for a while and said "Done". No IP address was assigned, according to
"/sbin/ifconfig".
3) I went back into Windows and tried the /release and /renew arguments to "ipconfig".
Here is the response I got:
H:\>ipconfig /release
Windows 2000 IP Configuration
Error: No adapters bound to TCP/IP are enabled for DHCP
H:\>ipconfig /renew
Windows 2000 IP Configuration
Error: No adapters bound to TCP/IP are enabled for DHCP
I'm pretty clueless at this point. Part (3) above suggests that DHCP isn't even being
used here, but I'm pretty certain that DHCP is indeed being used by my company's
network. What's the deal? Anyone have any advice? I appreciate it.
Erik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
