RAS-HELL
June 15th, 2000, 06:43 PM
Please help as I am going insane!
Get this:
My Server--NT4 server/SP5/DHCP running/RAS running/T1 LAN-internet-email-local workstations w/cat5/ ALL PERFECTLY FUNCTIONAL
My problem-- Remote Dialup via any WinNT or 2000 (clean install or not) system through conventional modem into our modem pool WILL connect, authenticate, assign IP, and have absolutely NO ACCESS to anything (internet, network drives, etc...). The network dialup monitor in the taskbar shows the system as transmitting but not receiving anything from the network. PING commands time out, but a TCP/IP connection is there. Plug a direct cat5 connection into the same machine and it functions as normal. To further complicate this, any Win95/98 system we have will dial up, connect, authenticate perfectly with identical dialup settings over the same modem connection.
Although, I have only once gotten a W2K system to actually dial in by setting up the system from scratch while directly connected to our LAN via cat5 cable...after completed install, the dialup will work for the most part but had a few reliability probs (which we wont get into). It seems it will only dialup properly on a system configured while connected to the lan and not seperately configured. Strange.
What I've tried-- Reinstallation of virtually every service/software/drivers/protocols on the serverside with anything to do with DHCP, TCP/IP, RAS, SP4 to SP5, AND on the workstation side: modem/lancard drivers, reinstall dialups, reconfigure dialups with static AND DHCP settings, reloaded clean O/S, tried different modem hardware, I am sure there's more but I can't remember.
This has been a thirn in my side for months now. Any assistance would save my sanity and be extremely appreciated!!!
Get this:
My Server--NT4 server/SP5/DHCP running/RAS running/T1 LAN-internet-email-local workstations w/cat5/ ALL PERFECTLY FUNCTIONAL
My problem-- Remote Dialup via any WinNT or 2000 (clean install or not) system through conventional modem into our modem pool WILL connect, authenticate, assign IP, and have absolutely NO ACCESS to anything (internet, network drives, etc...). The network dialup monitor in the taskbar shows the system as transmitting but not receiving anything from the network. PING commands time out, but a TCP/IP connection is there. Plug a direct cat5 connection into the same machine and it functions as normal. To further complicate this, any Win95/98 system we have will dial up, connect, authenticate perfectly with identical dialup settings over the same modem connection.
Although, I have only once gotten a W2K system to actually dial in by setting up the system from scratch while directly connected to our LAN via cat5 cable...after completed install, the dialup will work for the most part but had a few reliability probs (which we wont get into). It seems it will only dialup properly on a system configured while connected to the lan and not seperately configured. Strange.
What I've tried-- Reinstallation of virtually every service/software/drivers/protocols on the serverside with anything to do with DHCP, TCP/IP, RAS, SP4 to SP5, AND on the workstation side: modem/lancard drivers, reinstall dialups, reconfigure dialups with static AND DHCP settings, reloaded clean O/S, tried different modem hardware, I am sure there's more but I can't remember.
This has been a thirn in my side for months now. Any assistance would save my sanity and be extremely appreciated!!!