Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2003 routing and remote access

Status
Not open for further replies.

scsi050

Technical User
Aug 16, 2005
9
US
I have pc running 2003 enterprise, as a server. Connect is one onboard nic (called onboard) which is connected to a pppoe att dsl modem. The other nic is a pci nic (called lan). I got internet on this server to work, however it won't on the PCs that are connected to the lan adapter. DHCP, DNS works. I have visnetics deerfield firewall, but it is allowing all lan connections for the time being. Any suggestions?
 
Oh, also, the onboard adapter will not recieve an ip address from att, so i created a pppoe connection called att. That connection receives the ip address, the onboard get a 169. But internet still works locally.
 
You may need to enable internet connection sharing on the (onboard) interface that is connected to the internet.

This might be the simplest place to start.

Cheers

"Assumption is the mother of all f#%kups!
 
I don't want to use Internet Connection Sharing because it forces you to use 192.169 addresses, but i want to maintain my 10.0.0.0 network. That's why I want to use Routing and Remote Access.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top