Lost Network Connection with Statis IP

are the IP's that you are assigning statically different to those in the DHCP scope?

i assume this is Virus free network.
first some question ?
Still IP assign through  DHCP Server  ?
 domain or work group ?
how name resoluation work with you network WINS or DNS + DHCP ?

 as your above word "There is no any issue when we use DHCP.  But if we change DHCP to static IP "  mean  Workstation IP  change  Static and problem started after that   ?

Server running Statics with Static IP ( as a rule) and server not taking IP from DHCP , is it ?
where DHCP server installed ?

Switch or HUB installed with your network ?

 "Sometimes after reboot, we can ping for a while " , that mean  problem Seems to be Computer Browser service related problem. after starting  Browser election it will genertae high trafic. but after 20 min it will come to normal. is it ?

type this command on workstation (command prompt)
  net view
can you see shared resources ?

some defect network card or Cable loose connection or short circuit genarte high trafic. check agin

we can go to correct  way after you reply..

-Virus free network
-Whenever I switch back to DHCP, everything runs fine.  
-Domain
-WINS+DNS+DHCP
-Yes, if I change back from DHCP to Static IP, the problem comes back.

I attached the pings I did.  192.168.100.86 is from DHCP and 192.168.100.46 is static IP.

H:\>ping 192.168.100.86

Pinging 192.168.100.86 with 32 bytes of data:

Reply from 192.168.100.86: bytes=32 time<1ms TTL=128
Reply from 192.168.100.86: bytes=32 time<1ms TTL=128
Reply from 192.168.100.86: bytes=32 time<1ms TTL=128
Reply from 192.168.100.86: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

H:\>ping 192.168.100.46

Pinging 192.168.100.46 with 32 bytes of data:

Reply from 192.168.100.46: bytes=32 time<1ms TTL=128
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.100.46:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms



-No, servers can take IP from DHCP during installation.  DHCP server is on DC.
-I changed several switches to rule out switches problem.
-After 20 mins, it doesn't come to normal.  
-can't see with Net View and got error 121.
-rule out cable and NIC by changing many cables and computers for test.

Thank you for your asking and help

what about your scope settings in DHCP, when you set your IP's manually, are you giving the exact same settings that you give in DHCP addresses? DNS etc

-scope is 192.168.100.50 - 200
-exactly as DHCP.

Thanks

i mean are your settings identical.

in your options for DHCP, you can specify dns servers, routers, etc etc

are you static IP's set to the same settings

Yes, all IP settings using on static IP are the same as DHCP scope option settings.

deficult to think... anyway nice problem,

change workstation network card link speed to diffrent  values manually (remove automatic option) 100 full duplex, 100 half, 10 full and try again.

network connection  properties -->configure -->Advanced --> change  link speed

or try with another netwok card.

driver updates?

I used different computers from Dell and IBM (both desktop and laptop) and changed speed too.  Still get the issue.  

Finally I found that one of MIP settings in Netscreen firewall cause the issue.  Thank you very much for all you input and time.  

ah firewall fun!

ok,

can anyone explain why it responded  to ping as  follows,  I think it take few min to to start fire wall service.. is it ?

and also  not default configaration  with Firewall or configaration has been change by someone  and setting jamed.

{
Pinging 192.168.100.46 with 32 bytes of data:

Reply from 192.168.100.46: bytes=32 time<1ms TTL=128
Request timed out.
Request timed out.
Request timed out.
 }

It made a sense to me that first ping hit the 46 box and broadcasted to all network.  Then firewall picked up the first ping and told the sending ping box that firewall will accept the packets for box 46 and send them to Internet.  Then timed out.  Thanks

been a long time on this one, any luck, can you finalise this question

if someone resolved for you then accept and answer if not and you solved yourself

just paste a 0 point pointer Q in community support asking for this to be closed with your reasons

make sure you include the url to this page