Poor wireless signal will do this to you.
The 1000 rows - do they have text, image, ntext, varchar(max), varbinary(max), etc fields?
Try connecting to the other server using
where [SERVERNAME] is the name of the other computer possibly with an instance name such as OTHERCOMPUTER\MYINSTANCE.
You may find that "named pipes" performs better for you than a "tcp" connection or vice-versa. If you are using tcp and windows authentication then sometimes it can get slowed down whilst it looks for a domain controller, etc.
Could you mentally plot a graph of the following..?
1. Selecting 1 row
2. Selecting 10 rows
3. Selecting 50 rows
4. Selecting 100 rows
5. Selecting 200 rows
6. Selecting 500 rows
7. Selecting 1000 rows
If the problem is purely the amount of data then the time taken should be roughly linear. However, if #7 doesn't take much longer than #1 then you have some overall overhead with your network.