Discussion Locked

NT4 RAS with Exchange -

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a RAS server running on an older NT box with 2 modems, which, when dialed up on, connect users without a hitch. The problem for me, is that the Exchange server (running on a newer Dell PowerEdge) is inaccessible.

I can ping Exchange on the LAN. Using the modem/PPP client on the RAS, after connected, I cannot ping the Exchange server. Any suggestions - little help here!

Thanks,
Casey

9 replies

by hsorensen

Do you have an external IP for your e-mail and an internal IP for the Exchange Server? If so, try designating the Exchange Server's internal IP in the client's LMHOST file. e.g.;
192.168.x.x mail.somrthing.com

by cmkajue

Check the default route configuration on your RAS server. The default route should not be the IP address of the RAS server. If for some odd reason the default route on the RAS server has to be the same as its IP, then go into the command window and parse in the correct default route for the Exchange server.

Example:

Server A (RAS) - 172.16.1.10
Server B (Exchange) - 172.16.1.5
Server B (default route) - 172.16.1.1

In command window type:

route add -p 172.16.1.5 172.16.1.1

Cheers mate!

by daltonnetadmin

Is your Exchange server a member server on the main domain of your network?

I also set my exchange server up to authenticate against the NT4 domain login for each user. I have not had any problem after setting it up this way.

by aalger

Place an entry for the Exchange server in the LMHOSTS file of the client PC that is dialing into the RAS Server

by paul grinyer

Do you have manual WINS entries for the exchange server and the RAS server? Had a very similar problem once dialling in to an 16 port RAS server. Had to manually enter each server that had LAN resources to be used by remote clients and the RAS server itself then the problem went away.

PaAul

by paul grinyer

Do you have manual WINS entries for the exchange server and the RAS server? Had a very similar problem once dialling in to an 16 port RAS server. Had to manually enter each server that had LAN resources to be used by remote clients and the RAS server itself then the problem went away.

Paul

by andor.oudt

Didn't see this one yet:

What's the IP addres of the client. Is it the same as the segment the Exchange server is on. Did you configure the right route if it isn't.

Mhat's the status of the problem at this point?

This discussion is closed to new replies.