topic Re: Exceed in Operating System - HP-UX

Exceed

Gabriel Valdez_1 — Tue, 31 Jan 2006 11:33:11 GMT

Exceed will not work when using the static ip
172.16.10.204

But will work with Static ip 172.16.6.11

the first address gets outside the network the second is just pulled from the DHCP table

Re: Exceed

Jeff Schussele — Tue, 31 Jan 2006 11:35:39 GMT

HI Gabriel,

My guess is the first IP is not in the subnet that the switch resides & DHCP is giving you an IP in the proper subnet.

HTH,
Jeff

Re: Exceed

Jeff Schussele — Tue, 31 Jan 2006 11:43:55 GMT

Now that I re-read your post again I'm beginning to think you may have a firewall rule that's not allowing access from the first IP or subnet but is allowing it from the second.

Also you should check DNS for both IPs & verify that they resolve properly forward (by name) & reverse (by IP).

Rgds,
Jeff

Re: Exceed

Arunvijai_4 — Tue, 31 Jan 2006 11:47:29 GMT

Hi,

What is your subnet mask in both the IPs ?
It could be due to subnet mismatch.

-Arun

Re: Exceed

Gabriel Valdez_1 — Tue, 31 Jan 2006 11:51:22 GMT

Both addresses are in the 255.255.0.0

Re: Exceed

paolo barila — Tue, 31 Jan 2006 12:34:01 GMT

Do you have this problem only with exceed?
Does ping/telnet/ssh work?

Re: Exceed

Chan 007 — Tue, 31 Jan 2006 12:37:57 GMT

Gab,

Try from your windows desktop,
telnet 172.16.10.204.

If this works, then exceed will work.

If telnet fails,

then try following

ping
tracert

You will know what the problem is

Chan

Re: Exceed

Steven E. Protter — Wed, 01 Feb 2006 05:20:18 GMT

Shalom, Gabriel,

VLAN network setups commonly cause this problem.

Some IP addresses are accessible and others are not.

Its most likely the netmask division of the network and hostname causing this.

In many VLAN environments, ping and traceroute are not enabled, therefore you will have to use other services to confirm the networking environment.

SEP

Re: Exceed

Muthukumar_5 — Wed, 01 Feb 2006 05:22:35 GMT

Can you check as,

ping 172.16.6.11

ping 172.16.10.204

It will give you the answer. I hope routing or connectivity is not there to 172.16.10.204 machine.

--
Muthu