Routing & Remote Access ip address and resource error

  • Thread starter Thread starter darrien
  • Start date Start date
D

darrien

We have 2 windows 2000 machines. A domain controller with
exchange on it and a fileserver with routing and remote
access configured on it. They both sit behind a linksys
firewall. We have elected to use pptp for vpn connections
so 1723 was opened on the router and forwared to the
fileserver. We are using a private ip 192.168.(2).x with
a class "c" subnet on this network. Routing and remote
access was configured with basic default settings but the
assignment of address was set for 192.168.2.100-
192.168.2.149. The clients can vpn into the network.
They even appear in the remote access client with their
time. The are unable to view anything on the network
though. When running ipconfig from the client, the
address it keeps trying to assign is 192.168.(1).x. with
a 255.255.255.255 subnet. When i key in an address into
the clients pptp ip properties, it will accept the address
and still log in but still unable to access the network.
The subnet is still 255.255.255.255. Is the subnet the
reason that We are unable to view the network resources or
is there a bigger problem here? Is there a need to
install anything else like wins or open any other ports
for browsing? extra info. DNS is done by the domain
controller. DHCP for our network is done by the linksys
router. Thanks again for your help.
 
255.255.255.255 subnet is OK and that is by design. the question is why you
get 192.168.1.x ip. double check the VPN DHCP settings.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Back
Top