Click to See Complete Forum and Search --> : No access to file server


gamati
11-25-2002, 01:50 PM
I astabilish connection with my PC over infrared port, via ActiveSync. This is a software not only for syncronizing the Pocket PC, but also to share Internet connection, etc.
If I would try to open \\Attila\shared (which is a shared directory on my PC) the Pocket PC would answer:
There is already another device with the same name on the network. go to Start -> settings -> network -> id, and change id.
if i write an ip address like \\192.168.0.1\ the ipaq tries to connect, but it does not get any connection. the only way i can connect to my pc, and get files from it, is to run a webserver on my pc, and access it via http. Please, help me!
Thankx,

gamati

stevemw
11-25-2002, 07:03 PM
192.168.0.1 is a default IP addresses of the nework gateway; if you are using a hub and configured with dhcp and your host PC is getting an address from the hub you have to change the address of the hub's local area network IP address. If you change it to 192.168.99.1 and change the TCPIP configuration of your host compute to the same IP (192.168.99.1), the problem should be resolved.

gamati
11-26-2002, 02:37 PM
Actually, the IP address of my host computer is a static one and set to 192.168.0.1,
and the IP of the IPAQ is 192.168.55.101, and an ip address I do not know where to change, since i think it was configured by activsync, the software i use. but actually the IPAQ can find the ip for "attila" - that's my computer's name -, it can find the IP for it, but can't even PING it.

GAMATI

hatterofmaddnes
11-29-2002, 06:13 PM
Was reading your original post, might have a solution. Recently purchased wifi DLink card and working with file sharing with my PC. I, too, received the message that "computer on the network has the same name" I went into Settings/System/About/Device ID and changed the name from Pocket_PC to something else. I then went back to File Explorer and tried a network computer and it worked. I noticed that when I went to ActiveSync, it rename my sync folder and had problems syncing. I tried changing the Device ID back to the original to fix this problem and noticed that I could no longer get back to the network machine.
After you change your Device ID, maybe try a hardboot to make sure changes take effect. After that, you should be able to browse your network shares no problem.
One more thing I found tonight, if you want to play MP3z remotely accross the network, taking a playlist file you make in the MediaPlayer on your PocketPC and opening it up on your Desktop machine to view the contents. You'll notice its a simple text file with destination paths easy to make out. I tried it, and if you add a full network path and file name, save it back to the PocketPC and play it, it should work.

Hope this helps someone out.

stevemw
11-30-2002, 05:52 AM
Gamati is correct; I misread you original post (or rather your message got warped as it passed from my eyes to my brain).
It's more common to get a message about a duplicate IP rather than a duplicate name.

gamati
12-01-2002, 01:11 PM
Hello, again!

I tried it out... Now I have got another error message, I think it is a little bit better then the other one! :)
"Network path couldn't be found. Wether you do not have permission to log onto that network, or it cannot be found. Contact your system administrator."
If I ping my PC, i do not get the ip 192.168.0.1 but the INTERNET address of it. If I enter the internet address into the file explorer, I get the same error message. If I write it into the internet explorer, I can see the homepage running on my pc. (I have got a WEB SERVER on my PC)

I cannon understan what is going on here... :((

If you have any other suggestions, would you be so kind and write me?

GAMATI

MatthewSanders
05-06-2004, 03:21 PM
Hello,

I have been dealing with the problem of "A device with the same name...." error for countless hours now, and have just about pulled the remaining bit of hair that I have left out. First, I have a Toshiba e740 running Windows PPC 2002. I would change the device name and do everything that was suggested on posts such as this, but my PPC would only connect successfully about 1 out of 50 times. Since it did connect successfully on occasion, I decided to sniff the wireless network to see what was going on. What I noticed is that when trying to connect to a network share, the pocket PC would send a netbios name registration request to the wins server that was listed on my DHCP server. In most cases, the DHCP server would respond to the request. After that, the Pocket PC would send out 2 more netbios registration requests to the broadcast address. These would go unanswered. However, the notorious error would appear of "a device with the same name is already on the network". If I change the settings that the Pocket PC uses for win server to a bogus address, and change the address to static (with the gateway being listed as the broadcast address) it connects successfully. However, the connection negotiation is extremely slow. It does, however, work. I don't know how many other people are experiencing a problem quite like this.... Please let me know...

Respectfully,
Matthew W. Sanders

MatthewSanders
05-06-2004, 04:29 PM
Well,

It's me again. Just been fooling with this thing ("A device with the same name" error) non-stop, and I think that I have a solution that is a little easier to live with. I have noticed that if I soft boot right before I attempt to connect to a share (this involves powering off, and then pressing a combination of keys while simultaniously tapping a hole on the side of the device with the stylus) I can get it successfully connect every time with normal DHCP settings. Wow... Where is the warning (or better yet fix) on this bug. Obviously a software problem with Win PPC 2002. At any rate, Toshiba let me know that there will be no upgrade available for the e740 to WM2003. Hmm... Next time go HP or Dell, I suppose... At any rate, I hope this helps someone out.

Respectfully,
Matthew W. Sanders

gamati
05-07-2004, 07:40 AM
Hi! Wow I am impressed, how many posts I get to my topic.
You all just mixed one thing up: I connect my PDA to my PC via IRDA (infrared). All problems you were talking about where problems with WLan access.
Anyway thank you for your posts and help.

gamati