Ken S

This is a function of WM5, I sync both my iPaq 5555 and my Axim x51v using ActiveSync 4.0 on the same computer and only the x51v creates another network address. Oddly the ActiveSync window looks like AS 3.8 when I connect to the iPaq, and looks different when I connect to the Axim.

J-D-Cronin

what is : "another network address"?

Ken S

Sorry, guess I wasn't too clear, when I connect my Axim it creates a Network connection named "local area connection 3" which can be viewed under "Network Connections". This LAN3 is only visible when the Axim is connected to my computer. No network connection is made with AS 4.0 when I connect my iPaq so I assume that WM5 needs to connect through the LAN3 connection. Sorry if my terminology is a little off, I am definately not a network administrator.

iansel

Originally Posted by Ken S

This is a function of WM5, I sync both my iPaq 5555 and my Axim x51v using ActiveSync 4.0 on the same computer and only the x51v creates another network address. Oddly the ActiveSync window looks like AS 3.8 when I connect to the iPaq, and looks different when I connect to the Axim.

Absoloutely right . It is a function of WM5 not ActiveSync 4.0

I have just synced my old 2002 iPAQ and my X3 and neither of them created a new network conection. As soon as I synced the x51v a new network connection appeared on my Network Connections dialogue Device name is "Windows Mobile-based Device"

Ian

nath@nbriggs.com

Seeing x51v on network isn't really a security problem because the device has few if any attack vectors, worst that will happen is that avirus already on host pc will get copied to ppc.

It is an admin problem because many admins run a domain or equivalent with name lookup, talk nicely to your admin and he/she might help, we're people too

ps I'm a sucker for anyone who asks a favour and brings coffee/chocolate :-)

tostngdsnvoy

The X51v is not really on the same network as all of your PCS reside. The concept is the same if you have Firewire on your PC, you'll see a Network connection for that also, as Firewire can be used to connect two PCS together. If one of these PCs does NOT have an internet connection, and the other DOES, then while both PCS are connected by firewire, the non-networked PC may access the internet through the PC that does, without actually being on the network. This is because the PC with BOTH connections acts like a NAT (Network Address Translation)

The same is true for the X51v - The PC is acting as a NAT for the X51v, providing it with internet access. However, another PC can NOT access the X51v directly while it is docked.

I am a Domain Admin also, and I don't think you have anything to worry about, as it will not show up on any network IP scans unless the PDA is DIRECTLY connected to the network using either a NIC, WiFi, or BT LAN-to-NET

psionandy

cheers tostngdsnvoy... thanks for the info :approve:

__________________
You'd have thought that someone would have put a sig here
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

mkh

Mine shows up as Local Area Connection but it isn't visible to the network. Our network jacks are setup to disable themselves if a pc with an unregistered MAC is plugged into the port. My jack is still working implyig that the network doesn't see the Dell.

__________________
mkh

karmalized

I guess the idea behind this type of change from a Microsoft point of view, is that they are moving forward with WM5 to make it a more "Full" operating system, with features of full dekstops. As a network admin myself, I would rather my x51v show up on the network as a computer, as that will give the x51v more functionality as computer, then as a simple PDA. Seeing as you have programs like pocket putty, and term service clients on the PDA, they could then be used to expose old weaknesses or make new ones (and trust me, patching security holes due to rogue devices, is a far harder job then most know about).

The question of security becomes one of local security protocols. Due to a change like this by Microsoft, you will probably find more and more admins ban the devices from networks, as it would now be possible to have bluetooth, 802.11, ethernet, viral and multiple other weaknesses on the networks. Not only while you are work, but while carrying a copy of a virus on your PDA from home or from Starbucks or wherever.

I see this as an annoyance for the people who have to abide by network administrators rules, but at the same time it makes the PDA a fully functioning computer. I guess putting Norton's anti-virus, and airscanners firewall would be recommended for those people who will need to explain the new "hole" on the network. As the x51v has enough juice to run anti-virus and firewall programs, I ensure mine has it.

eichmat

From what I can tell when I plug my wife's new x51v in to her PC, it creates a "network connection" between the PC and the Windows Mobile device. The "network" is between the PDA and the PC via the USB cable and doesn't appear to be visible to anyone outside that "network" (can't be pinged, etc.).

That being said, any internet activity from the PDA will undoubtedly be visible to a network admin, but that's no different than your pre-WM5 PDAs (it looks like traffic from the PC itself). Just a cursory glance at the logs on my router show that surfing on my wife's x51v just shows up as requests from the PC (granted, detailed packet inspection might show clues that the activity is from a PDA, but hey, if they're looking that closely, you've got other issues...).

Now obviously, if she was using her WiFi to connect to our network, that would show up as a new machine on the network--but again, no different than under previous versions.

Now--my only complaint is the lack of WiFi based ActiveSyncing...

MetalHead

The ultimate next step for the PPC running WM5 or WM? would be to attach to the network with it's own address and become part of Active Directory as a domain member because at that point an administrator could apply security policy based on the machine type. This would definately be handy, especially if you could control the port activation/deactivation of WiFi and Bluetooth not to mention presenting necessary patches automatically through patch management. I would think at that point administrators would actually welcome this situation, provided of course as mentioned before that AV was also a forced package.

__________________
'All Your Base Are Belong To Us'

Free Stuff - psShutXP (B&W Skin), WiFiFoFum, GNU Backgammon, MH Conversions & MH Formula calculators.
Purchased - Wisbar Advanced2, Spb Pocket Plus, WeatherPanel, MemMaid, Resco File Explorer, Juni's Black & White Skin. Bejeweled 2.