Connection by ISDN

  • Thread starter Thread starter Slawek
  • Start date Start date
S

Slawek

Hi,

My server (windows 2000 SBS) have got connection to the internet by DSL.
The server have got ISDN modem for incoming connections. If I connect to the
server from another, client computer by ISDN modem client can access to
server's resources and to LAN but haven't got access to the internet.
The server is domain controller and ISA Server is runing.
What can I do to make internet accessible?
It is routing problem?


Slawek

P.S.
Sorry my English is bad.
 
One possibility could be that the LAN clients are accessing the internet via
NAT. In this scenario, add the internal interface on the server as the
private interface of NAT.

The other possibility is if you are having a proxy server to access the
network, do the clients have the correct proxy settings in IE?
 
Note that in W2k you can't do this from the RRAS console (you can in
Server 2003). See KB 310888 for the netsh command required in W2k.

Kadirvel C Vanniarajan said:
One possibility could be that the LAN clients are accessing the internet
via
NAT. In this scenario, add the internal interface on the server as the
private interface of NAT.

The other possibility is if you are having a proxy server to access the
network, do the clients have the correct proxy settings in IE?



--
Kadir

(e-mail address removed) [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.

Slawek said:
Hi,

My server (windows 2000 SBS) have got connection to the internet by DSL.
The server have got ISDN modem for incoming connections. If I connect to the
server from another, client computer by ISDN modem client can access to
server's resources and to LAN but haven't got access to the internet.
The server is domain controller and ISA Server is runing.
What can I do to make internet accessible?
It is routing problem?


Slawek

P.S.
Sorry my English is bad.
Click to expand...
Click to expand...
 
Hi,
Note that in W2k you can't do this from the RRAS console (you can in
Server 2003). See KB 310888 for the netsh command required in W2k.
Click to expand...

If I run the command: netsh routing ip nat add interface internal private
system answers: "First it is necessary to install: NAT."

If I run the command: netsh routing ip nat dump
system answers:

# ----------------------------------
# Konfiguracja NAT
# ----------------------------------
pushd routing ip nat
uninstall


popd

In "Routing and Remote Access" NAT protocol is configured. They are
following interfaces there: "LAN Connection" and "Internet Connection".
I can't add "Internal" interface.

Slawek
 
With W2k, you cannot see the internal interface in NAT from the RRAS
console. That is why you need to use the netsh command to add it as a
private interface in NAT. (This has been fixed in W2k3, and you can add the
internal interface from the RRAS NAT console).

I have seen the message you are getting, but only when NAT has not been
configured.
 
Back
Top