ICS - logon problems through ICS connection

[Guest]

We have a unique configuration. We have a machine (Windows 2003 server)
running ICS. Client PC is on the LAN side of the connection and another
Windows 2000 server/domain is on the other side of the connection (Internet
side). The client PC can connect to the Internet (http) without any
problems. We can see the domain on the client PC but cannot log onto that
domain or connect to any shared resources on the other side. All connections
are full ethernet, not dial up/DSL/cable.

Any suggestions? I have tried both ICS and NAT on the Windows 2003 server
with the same results.

 

[Robert L [MS-MVP]]

1. assuming the w2k3 is the server between LAN side clients and the w2k dc,
do you mind to tell us why you do that?
2. based on above assumption, I would enable IP lan routing instead of ics.

3. if for some reasons, you need to use ics, I would prefer to use NAT
instead of ics on 2003.

4. logon issue: can you ping the dc by ip? if yes, can you ping it by name?


--
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.


Bob 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.

 

[Bill Grant]

Logging on through a NAT router is a known problem. The basic
recommendation is "don't do it". The problems are similar to trying to do
domain logons through firewalls.

The only KB article I can find is 843427 .

 

[Guest]

The reason for the configurtion is because the network police will not let us
add any machines to the current network so we are trying to connect new
machines through a NAT translation to hide them from the police. Long story.

We tried both ICS and NAT with the same results. We can get the the pdc
when we use http but not with a network logon.

Bruce