TCP/IP on startup
This is a discussion about TCP/IP on startup in the Windows Networking category; What does win2k do to TCP/IP on start up? The reason for this Q is that it messes up my TCP/IP up. After a restart, I can't connect to FTPs. It gets in, but when I do a List or Dir command, it can't open a data connection.
What does win2k do to TCP/IP on start up?
The reason for this Q is that it messes up my TCP/IP up. After a restart, I can't connect to FTPs. It gets in, but when I do a List or Dir command, it can't open a data connection. Everytime I need an ftp connection, I have to re-install TCP/IP. Then it works fine for that session, but after I restarts, it goes back to "not able to establish data connection".
Anyone have any ideas?
The reason for this Q is that it messes up my TCP/IP up. After a restart, I can't connect to FTPs. It gets in, but when I do a List or Dir command, it can't open a data connection. Everytime I need an ftp connection, I have to re-install TCP/IP. Then it works fine for that session, but after I restarts, it goes back to "not able to establish data connection".
Anyone have any ideas?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
