WT2 - Wireless transmitter. Please help!!

Posted: Fri Aug 03, 2007 9:59 am

I treated myself to the Nikon wireless transmitter (WT-2), so I can now take a shot and it immediately appears on my laptop

Or at least it's meant to!!

I consider myself reasonably techy and reasonably au fe with networking etc. But I'll be damned if I can get the two to talk to each other. I'm close to getting it working and have trawled through most of the Nikon support documentation and online blogs/threads, but still no dice. Has anyone got one? Can anyone shed any light on what I might be doing wrong?

I've set it up as an ad-hoc network, so I don't need any router, it's directly from PC to camera.

On the PC end, I've given it a static IP address (picked arbitarily) - 10.25.1.1 and enabled the FTP server, allowing anonymous login. Wireless network wise, I've added an ad-hoc network to my preferred wireless network list, giving it an SSID of "D2X" and for simplicity, I've also turned off WEP or any security.

On the camera, I've set it up to transfer files via FTP, logging in anonymously. I've given it a static IP address of 10.25.1.2 (both share the same subnet mask - 255.255.255.0), same SSID (D2X) and all encryption turned off. I also enter the ftp server address as being 10.25.1.1

So, when I turn on the camera, my laptop sees the second ad-hoc connection and it connects to the D2X network. From the command prompt, I can ping my laptop (10.25.1.1) and also ping the camera (10.25.1.2). To test the ftp service, I also ftp'd in (ftp 10.25.1.1) and all seemed OK.

But on the camera it keeps telling me it can't find the server (10.25.1.1). If I give it a crap/bogus IP address, it comes back immediately saying it can't find the server. If I give it anything in the same network (10.25.1.xxx) it takes it's time but eventually comes back saying it's unable to find the server!!!

I've read some threads where,white space following the IP address in the server field on the camera has caused problems, but to the best of my knowledge I've deleted all additional white space. So that's where I'm stuck

Any help greatfully appreciated

Ciaran

--
http://www.thewonderoflight.com

Joined: 04 Jun 2006 Posts: 114 Location: Knoxville, TN

A couple things to check:
1: make sure you are on a private network either disconnected from the internet or behind a router with network address translation turned on. If you're router has access to the internet, it could be looking for the ip address on the WWW. Try a 192.168.x.x (private networking range)address and it may work for you. Private networks with other ip ranges usually require much fancier routers.
2: x.x.x.1 on a 255.255.255.0 network is the gateway and may be in use by the router itself. Try other values and see what you get. (meaning that it may be that the router thinks the packets are for it)

Hopefully one of the two sould help you.
Michael

Joined: 05 Mar 2006 Posts: 18 Location: Champaign, IL

MBChamberlain wrote:

Try a 168.192.x.x (private networking range)address and it may work for you.

I think you mean 192.168.x.x...

Rob

Joined: 04 Jun 2006 Posts: 114 Location: Knoxville, TN

colemanr wrote:

MBChamberlain wrote:

Try a 168.192.x.x (private networking range)address and it may work for you.

I think you mean 192.168.x.x...

Rob

Yaeh, srory lysdexia knikicg in.

Private networks are indeed 192.168.x.x

Mciehal

Posted: Mon Aug 06, 2007 11:35 pm

MBChamberlain wrote:

Try a 168.192.x.x (private networking range)address and it may work for youl

I think you mean 192.168.x.x

Posted: Mon Aug 06, 2007 11:37 pm

colemanr wrote:

MBChamberlain wrote:

Try a 168.192.x.x (private networking range)address and it may work for you.

I think you mean 192.168.x.x...

Rob

I should continue reading the thread before I post my response, in this case left intact for amusement's sake.

Posted: Fri Aug 10, 2007 11:21 am

Hey, I think you mean 192.168.x.x .....

(hehe)