Quote:
Originally Posted by gTen
The terminal thing is for debugging..it is not in config but under connection settings when I click properties on the dialup but in win 7 they changed connection settings so not sure where it would be.
Just to confirm aside from that you followed the direction exactly? and dialing #777? also did you disable windows mobile center?
|
Got pretty much everything except the terminal window. No go still.
But will keep working @ it .
Your friend did have a Sprint TP2 right? Did you use the ICS and MWodem fix.cab or only make the reg changes (only the ones specifically mentioned in the mogu thread) manually?
Trying to see exactly what made the difference since the symptom of being stucked @ the login you described exactly like me so it must be the same prob to start w/
Quote:
Originally Posted by niteriderxp
If you use Dial Up Networking (DUN) to connect to the internet on your phone, you are more likely to transmit the DUN NAI when you authenticate. If they see you authenticate using your DUN NAI, they can charge you for it.
I did this a few years ago and to ensure I wasn't detectable I would change the DUN NAI in EPST to match the regular NAI. That being said Bluetooth DUN should work without any additional software if the DUN NAI has been changed. It will also give you a non-NATed public IP.
An annoyance that I have had with DUN is that you have to turn off all internet bound applications including Activesync before you dial up, otherwise they tend to disconnect your session.
In terms of VPN, I use PPTP to connect to work and never had any issues with it over ICS. Now if your company uses IPSEC, the protocol is a bit more complex and does not like traversing NAT.
|
wouldnt be surprised it they do use ipsec. IT@my place real screwy and not helpful. Thanks for tip on NAI...