Can't see Shared Resources of server

[wdfrankel]

Recently the corporate network admin had my office change the ip address of an application server (to an "external" ip address outside of the firewall; "Internal" ip addresses are on a totally different Class A subnet). The app server is still on the same network domain as the Primary Domain Controller in my office, and I can log in as a network user, but I cannot see the server in windows' Network Neighborhood. I also can't see the rest of the network domain from the app server's Network Neighborhood.

The PDC server is on NT 4.0 and the app server is Windows 2000 Pro. When I use the NT "Server Manager" to try and look at the properties and shared directories on the app server, it just pops up a dialog saying "Access Denied." The proof that the app server is on the domain is the pressence of the (grayed out) icon in Server Manager and the fact that I can log into the app server as a network user.

Is it possible to share computer resources across the network when the shared computer is on the network domain but the IP address is different than normal IP Domain of the Primary Domain Controller?

If so, how can I set up a "Trust" relationship to accomplish this?

Thanks,
David

 

[Jpoandl]

"Recently the corporate network admin had my office change the ip address of an application server (to an "external" ip address outside of the firewall; "Internal" ip addresses are on a totally different Class A subnet)."

Based on the above statement, I would say your server is now outside of your internal network. The firewall is blocking ports to proctect your internal network.

The reason, you can't "see" your server has nothing to do with the IP address. I think it's your firewall that is causing the problem. I bet if you look at the event log on the NT server, you will find that it can't "see" the domain.

You have to enable certain ports on the firewall to allow this server to "talk" to the internal network.

I bet when the server was moved and the IP address was changed, the change did not get updated in WINS or DNS. Can you PING the server by name? How about by IP address?

You might want to try to map a drive using the IP address of the server rather than by NAME.

Having the server on a different subnet shouldn't be a problem at all...assuming that you have a gateway (ROUTER) that can route packets. When you changed the IP address of the server, your GATEWAY address should also change.

---hope this helps...let us know if you still have questions..

Joseph L. Poandl
MCSE 2000