router/proxy issue over ethernet

[javier22]

I am administering a private NT4 network.<br>About 1/4th of the pc on my network are able to access the pop3 server we use on a remote network. The other 3/4ths can't find the remote server, can't ping its ip. They can ping other machines within the lan, and they can ping the gateway address (this is a lucent pipeline 50 isdn to ethernet router. Router configuration is: Nat is turned off. RIP Policy is poison reverse. ARP Proxy is off. <br>Router DHCP is off.)<br><br>They are unable to ping outside of the lan. i have tried to discern any relevant differences between the stations that can get out and those that can't, but cannot find any. -What makes this even more perplexing is that all stations are able to access the internet via Microsoft Proxy Server. <br><br><br>This is becoming quite a problem, as you can imagine. Any help would be greatly appreciated.<br>&nbsp;

 

[Zelandakh]

If some are able to get out and some are not it must be machine based and not router based.<br><br>Type ipconfig/winipcfg into a reply - one for a pc that works and one for one that does not. Also give details of router IP and mask.

 

[state]

Before you do anything you need to solve you connectivity issues first. Remember &quot;You ain't got a thing, if you ain't got that PING.&quot; <br><br>Are the 25% of PC's that can ping on a different subnet? If so the router configuration needs a static route for both segments to the LAN segment housing the pop3 server. Are there any other devices (hubs, switches, routers, firewalls, etc.) between the 75% of non responding PC's? If so, make sure they are configured to pass traffic to each other. Also make sure the subnet masks are correct.<br><br>Hopes this helps.