Then: Was able to telnet, ftp to solaris box, from its netowrk as well as other connect networks.

Did: Simple reboot, came up fine (multiuser).

Now: Unable to ping, telnet, ftp.

Question: What could have changed during a reboot to not allow remote access or even a ping. The solaris box can however ping other boxes on its network. but unable to send/receive from boxes on other networks.

Can you make sure that the machine (in question) has appropriate local routing table? Is the NIC configured with the correct IP & Netmask? What are the error messages you are getting when you try to ping, telnet or ftp? You can have hints from error messages.

You know that if you make temporary change to solve some problems, a power failure or reboot will bring them back. Have you done something similar lately?

On the Solaris box in question, what results do you get from an

ifconfig -a

command? also can you ping localhost and get a reply? If somehow your driver binding has messed up with your NIC you could see if a boot -r from the ok prompt will fix it.

Also, did you try /etc/init.d/inetsvc stop then /etc/init.d/inetsvc start to see if that makes any difference?

May be worth checking /etc/inetd.conf to check if it's corrupted. Also /etc/services.

If you go to this solaris box, can you actually run ping commands or any other command or do you get an error? If you can't run commands then it's possible there's a problem with /usr or it isn't mounted I guess. (in which case edit /etc/vfstab)

One more thing I can think of at the moment (sorry I'm tired) is stopping the system, sync, then running a manual fsck. (restoring a superblock backup may also be worth trying).

Cheers

Thanks for your replies.

/etc/services
/etc/inetd.conf
ifconfig -a

All of the above seem to be in order.

I can ping/ftp/telnet to other machines from the box in question. So it looks as if the NIC/OS is working as it should be. I just cant connect to it from a location that I have many times in the past. I dont get any errors when trying to connect aside from a 'connection time out'.

Someone must have made a network related change recently...figures.

Craig