Trying again....DHCP, mapped drives, ip

[Kenneth]

This is a repeat of an earlier post. Since it seems Fred seems to be having
the same problem I thought I'd bump this up early in the morning hoping it
wouldn't get lost in the multitude of posts.

I've culled through the many threads here trying to find the fix for the red
x on startup. I've tried everyone I've found and nothing seems to work. I
was poking around under the admin tools/event viewer/system and found the
following error being reported:

The IP address lease 192.168.1.113 for the Network Card with network address
00508D535420 has been denied by the DHCP server 192.168.1.1 (The DHCP Server
sent a DHCPNACK message).

I did a search on google and saw the mention of assigning ip's through the
respective router (I have a Linksys). Not having much knowledge on the
subject of DHCP and assigning ip's I was wondering if before I invest the
time learning how if this could potentially solve the problem of not
connecting to the shared drives on startup. Or if it would be just another
thing to throw in the brain matter when I have time.

Our network consists of 11 computers one acting as the "file server" and the
rest of them accessing it. All computers are running XP Pro.

Thanks for any help,

Kenneth

 

[Eric]

Look through this:
http://perso.wanadoo.fr/haikal/Router/router_forum/RT314%
20Connection%20stalling.htm
Hope it helps.
Eric

 

[Gzale MCSE]

Sounds like your machine has a static IP in it's
configuration. go to the properties of local area
networkthen to properties of tcpip change to get ip
automatically. Or if all your machines are configured with
static ip's open up the control panel of the router go to
the DHCP tab and turn off the DHCP Server. If All your
machines are configured for automatic IP addressing and
the router is 's dhcp is and should be turned on check the
dhcp table and delete the entry for 192.168.1.113.click
apply then go to the offending machine start run type cmd.
at the prompt type ipconfig /release then ipconfig /renew.
hope this helps let me know

 

[Dan]

If his machine had a static IP it would not be doing a
DHCP broadcast and receiving a nack.

Most likely what you have here is TWO dhcp servers, one on
the Linksys and one on the Win file server, both trying to
answer the same ack. This could cause a delay in getting
an IP address. If this is the case, turn dhcp on the
Linksys off.

 

[Kenneth]

Dan,

Is there a way to check if Win file server is running dhcp? Or is it just a
matter of turning it off on the Linksys to see what happens? I assume if I
do turn it off on the Linksys and everything continues to work dhcp is
running on the server.

Thanks,
Kenneth

 

[Guest]

Folks, if there were 2 DHCP servers attempting to issue IP addresses on the same network, one of them would take over and cause the other to disable it's service. My theory is that with these small networks using Cable/DSL routers with DHCP enabled may be interfering with connections to the server. Thought process is to statically assign IPs to each PC and the server and turn off DHCP at the Cable/DSL router. Reason for thought process: If all PCs (including the server) are connected directly to the Router and the router is responsible for the IPs assigned to each NIC, then each PC would first go to the Router to obtain it's IP address and at the same time to the server to reconnect the mapped drives. In addition, the problem is intermittent and can occur on any machine, but only on one machine in the workgroup. I have not seen this on multiple machines concurrently

I have a Client experiencing this very issue. My next steps are to statically assign the IPs to the NICs and turn off DHCP at the router

Point of interest: If in a domain environment, this issue does not occur

----- Kenneth wrote: ----

Dan

Is there a way to check if Win file server is running dhcp? Or is it just
matter of turning it off on the Linksys to see what happens? I assume if
do turn it off on the Linksys and everything continues to work dhcp i
running on the server

Thanks
Kennet

 

[Rob Elder MVP-Networking]

One DHCP server will not disable another DHCP server. The only exception to
that rule are if you are running a 2000 or 2003 domain controller, any
unauthorized 2000 or 2003 DHCP servers will be shut down.

What exactly is your problem? Is the client receiving wrong IPs? any IP
addressing at all?

Folks, if there were 2 DHCP servers attempting to issue IP addresses on

the same network, one of them would take over and cause the other to disable
it's service. My theory is that with these small networks using Cable/DSL
routers with DHCP enabled may be interfering with connections to the server.
Thought process is to statically assign IPs to each PC and the server and
turn off DHCP at the Cable/DSL router. Reason for thought process: If all
PCs (including the server) are connected directly to the Router and the
router is responsible for the IPs assigned to each NIC, then each PC would
first go to the Router to obtain it's IP address and at the same time to the
server to reconnect the mapped drives. In addition, the problem is
intermittent and can occur on any machine, but only on one machine in the
workgroup. I have not seen this on multiple machines concurrently.

I have a Client experiencing this very issue. My next steps are to

statically assign the IPs to the NICs and turn off DHCP at the router.