I posted this also at BBR ..
Ok ..
So here at the office i have auser who has to dial into a production environment as hes a developer and he has to work with the client to demonstrate the application, blah blah
There is a LAB and Production environment. 2 diff locations, boxes, etc.
Both are configured the exact same way except different numbers to dial into obviously. Also they both have the "terminal after connection" setting also.
Well, he can dial into the LAB, authenticate and work as normal. The production however; nothing can be typed into the terminal after dial-up. It just sits there at the prompt. He was able to connect nearly 2 weeks ago. Now connecting is a no go.
So i decided to try the connection on my own laptop and the connection is a success as well as typing into the "after connection dial up window" .. I've updated the drivers, both laptops running Windows XP. Since then i've actually had to give the user another lower-level laptop which works and can type into the terminal after dialup.
I have reinstalled modem drivers, done diagnostics and everything is in working order.
So i decide to try it on a desktop and guess what. The connection will not work on some desktops also. This just doesnt make any sense to me.
What can possibly cause such odd behavior?
Where should i start?
Is it possble some provisioning on the other end caused such an unreliable connection to it?
Thanks in advance.
Lenny :.
IT Guy :.
.::Get in where you fit in and where you need to fit in::.
Ok ..
So here at the office i have auser who has to dial into a production environment as hes a developer and he has to work with the client to demonstrate the application, blah blah
There is a LAB and Production environment. 2 diff locations, boxes, etc.
Both are configured the exact same way except different numbers to dial into obviously. Also they both have the "terminal after connection" setting also.
Well, he can dial into the LAB, authenticate and work as normal. The production however; nothing can be typed into the terminal after dial-up. It just sits there at the prompt. He was able to connect nearly 2 weeks ago. Now connecting is a no go.
So i decided to try the connection on my own laptop and the connection is a success as well as typing into the "after connection dial up window" .. I've updated the drivers, both laptops running Windows XP. Since then i've actually had to give the user another lower-level laptop which works and can type into the terminal after dialup.
I have reinstalled modem drivers, done diagnostics and everything is in working order.
So i decide to try it on a desktop and guess what. The connection will not work on some desktops also. This just doesnt make any sense to me.
What can possibly cause such odd behavior?
Where should i start?
Is it possble some provisioning on the other end caused such an unreliable connection to it?
Thanks in advance.
Lenny :.
IT Guy :.
.::Get in where you fit in and where you need to fit in::.