I've mentioned this in other posts but haven't seen anyone else comment. I have no problem with either AS 4.1 or 4.2 except for the fact that I have no connection to the Internet (via my PC) when the phone is cradled when using 4.2. (This is pass-thru, not tethering.)
My settings in AS are the same but I get an error message from PIE when 4.2 is installed. 4.1 works as it should.
No problem here- device is in the cradle as I post this. I have no clue as to what would actually fix your issue, but if it were me I would try uninstalling the samsung tethering drivers.
i am also experiencing this problem. I cannot connect to the internet through pass through activesync. I have tried all sorts of methods (turning off antivirus, firewall, etc) and i have set connection to 'the internet' and etc. I am still unable to access the internet when docked.
I'm bumping this up now that AS 4.2 has been released. With 4.1 still have no pass-thru issues. With 4.2 and WM5 pass-thru simply doesn't work. Other than upgrading or downgrading AS, nothing on the device or computer has changed.
This is about the end-of-the-road when it comes to i730 gurus. Any thoughts?
all i can say is ive been using 4.2 beta and i have been running VZW WM5 for about 2 months now and i have no problems with the pass through internet connection to the phone when cradled. i just tried to access my yahoo mail from the phone while cradled and it works fine. i pop my gmail every 5 minutes when its cradled too.
you tried turning off the windows firewall? try turning it off completely. id try that first and scale down from there.
No firewall is involved. Ports have been opened and closed in router, etc. I've installed, uninstalled, reinstalled, etc. 4.2 refuses to let me pass-thru. Dropping back to 4.1 always resolves the issue.
I expect it's going to take a bit of a "guru" to solve this. Whatever it is, it isn't obvious. (Or soooo obvious, I'm missing it.)
so it is turned off? my interpretation of "no firewall is involved" is you thinking that no firewall is involved because your not running a hardware firewall like a PIX. but you might be running a software firewall like windows firewall.
Just trying to understand the issue- presumably your PC has its own connection to the internet, so- if your device is in the cradle next to the PC, and you are NOT trying to tether, why would you want to use PIE on the device to connect to the internet, instead of the PC's browser, which no matter what brand of browser, has to be better than PIE.
Only explanation I can think of is that your PC only has dialup speed, and device has EVDO. Otherwise there doesn't seem to be a reason to do it.
Also, if your PC is part of a network, it may be the network's firewall, not the PC's, which is causing the problem.
I have the same problem with AS 4.1. No, it is definately not a firewall issue. I am on Windows 2000 with no firewall installed. Yes, it worked before I upgraded to WM5/AS4.1. Why do I want it? Because, I WirelessSync to Lotus Notes for work and do not want to have to disconnect from AS to have to WirelessSync. I use AS both by USB and Bluetooth, same problem in both. This definately should work. I did install and remove PDANet. I also have installed the BTModem.
I also posted about this trouble in http://pdaphonehome.com/forums/551224-post11.html .
Help, this is the one thing wrong with WM5.
Supported Operating Systems: Microsoft Windows 2000 Service Pack 4; Microsoft Windows XP Media Center Edition; Windows Server 2003 Service Pack 1; Windows Server 2003 Service Pack 1 for Itanium powered Systems; Windows Server 2003, Datacenter Edition for 64-Bit Itanium-Based Systems; Windows XP Professional 64-Bit Edition (Itanium); Windows XP Service Pack 1; Windows XP Service Pack 2; Windows XP Tablet PC Edition
Quote:
Originally Posted by raq1025
I have the same problem with AS 4.1. No, it is definately not a firewall issue. I am on Windows 2000 with no firewall installed. Yes, it worked before I upgraded to WM5/AS4.1. Why do I want it? Because, I WirelessSync to Lotus Notes for work and do not want to have to disconnect from AS to have to WirelessSync. I use AS both by USB and Bluetooth, same problem in both. This definately should work. I did install and remove PDANet. I also have installed the BTModem.
I also posted about this trouble in http://pdaphonehome.com/forums/551224-post11.html .
Help, this is the one thing wrong with WM5.
Yes, Win2k is fully patched SP4 plus all updates available from Microsoft. Actually, it's a pretty clean install. I just did a wipe and clean install with minimum of programs installed. The condition existed before I wiped also.
However, 2 weeks ago. I got a message on the phone when craddled that the phone couldn't get an IP address. I never knew it wanted one. Now everytime I craddle I get the same message. When is it ment to get an IP from ? My Router, via DHCP ?
I would like to surf or check email on the phone when craddled.
I'm using Active Sync 4.2 on Windows XP SP2 on machine and the other machine (which when craddled does the same) active Sync 4.1 on XP all the latest SPs.
I am running into the same problem with Windows XP Service Pack 2 and ActiveSync 4.2. My ppc6700 won't pass through. Just thought that might help rule out the samsung factor.
I don't have a solution for you but there are a couple tools available that might help you narrow the problem down or provide screenshots so that somene else here may be able to help.
1) There is a free today screen plugin that will allow you to see what ports and IP addresses are in use when the PPC is connected to the host computer. Perhaps comparing your results with those of another may help you. The plugin is available here: http://www.pocketgear.com/software_detail.asp?id=10423
Hopefully these tools will help you diagnose the connectivity issue you are seeing.
I have a similar issue but it only occurs when I am connected at work through the corporate network (I suspect i've got a subnet mismatch or given our network uses the 161.xxx.xxx.xxx IP set it doesn't like the 161.254.2.2 from the Pocket PC). When I'm connected to the same laptop at home or my home PC pass through works just fine.
__________________
LG Phenom, Casio E-11, Casio E-105, Casio E-125, I730 WM5 W A2DP, xv6800 WM6.5.
The PPC's IP address won't be passed to the corporate or any other network when it's cradled. The IP address used will be the one assigned to the computer it's connected to. 169.254.0.0/16 addresses are not routeable on the Internet if the ISP follows RFC standards, and the routers supporting your network won't know how to reach them (unless your workstation is actively advertising routes, which would be very, very rare). On most corporate networks, you'll see addresses that are 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 assigned.
Have you tried waiting for the sync process to complete before attempting to browse the Internet from the PPC? When my phone is first connected via USB, I can't reach anything up until AS reports a status of "Synchronizing." Then everything works, although quite slowly while the sync is running.
You might go to AS and look at "File->Connection Settings" and make sure that either Automatic or "The Internet" are selected. If "Work Network" is selected, the PPC is going to assume that it can only reach the Internet through a proxy server (because that's just how dumb it is) and die on the vine under most circumstances.
If you are looking for good tools, I'd recommed vxIPConfig and vxUtil from Cambridge software. Both are freeware and available at http://www.cam.com/windowsce.html. They aren't Today Screen plug-ins, and they're a bit dated, but they work great, cost nothing, and provide a great range of tools.
Internet passthough broke for me as well as soon as I upgraded to 4.2. using WM5.0. read elsewhere that reverting back to 4.1 solves the problem for most. Came here hoping someone had some info, hence my first post
Glad to know I'm not alone. After all, misery loves company. I've certainly hunted the web, newsgroups, MS's site -- to no avail. At best, I've come across some others who have had the same problem.
Interesting, too, since one of the "benefits" of the 4.2 upgrade is supposed to improve pass-thru issues. Oh well.