General discussion

Locked

0.0.0.0 IP

By BalaSubramanian ·
Hey Guys,
I gotta Application server running on Win NT server, which has a static IP address (172.31.105.71). Im running a Schedule job that logs Netstat results every min, so that i could monitor the network status of my machine.

The problem is that at inconsistent time intervals, Netstat -n shows me IP address 0.0.0.0
as my Local Address. Im aware that the IP address 0.0.0.0 is while listerning. But the fact is Netstat shows 0.0.0.0 after some remote machine, which has nothing to do with my app. establishes a connection with My machine.

ie.,
TCP 0.0.0.0:135 a.b.c.d:xyz ESTABLISHED

After this happenes, all my applications services, that connects to my SYbase server, LDAP and SQL Sever fails. The problem gets resolved after i reboot my machine.

Since im not a network guy, im quite confused by this behaviour. Can you guys throw some light on this.

Thanks in advance....

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Well

by voldar In reply to 0.0.0.0 IP

An IP address 0.0.0.0 means that your DHCP server has no more IPs in the range to provide one your computer. The fact that you have a STATIC IP, well, that makes things sound odd. Is it 100% sure that you have static IP? Or is it a reservation on your DHCP server? Check this out, and then, come back here - or better - ask your question in the Questions & Answers section of TR.
Best of luck.

Collapse -

by BalaSubramanian In reply to Well

hi vladolar...
Im quite sure that my application server makes use of static IP only. Its is not any reservation on DHCP Server.
Iam wondering is it a network issue or some kinda virus in my network :-(

Collapse -

IP Conflict?

by ksreid In reply to

Have you had any IP conflicts on your network for the IP address that you are trying to statically use on your App server?
If you have an address statically assigned to your app server, you really should have it set as a reservation on your DHCP server otherwise the IP is available in the table and could dynamically assigned to another system, causing IP conflicts.
I would set a reservation for your servers ip anyway, just to be safe.

Back to IT Employment Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums