Oakley is right on: You need to define the RSLinx Gateway computer as the DDE server, with syntax like
\\ComputerAName\NDDE$|DDESHARENAME!N10:0,L10
I want to add some comments for completeness. Let's agree to call the computer running RSLinx Gateway "Computer A" and the laptop running RSLinx "Computer B".
RSLinx Gateway has two different ways to get data to remote computers.
The first is "RSLinx Gateway" mode.
In this mode, RSLinx on Computer B can use Computer A's RSLinx drivers (DF1, DH485, DH+, ControlNet, etc.) as though they were local. Comms takes place using native RSLinx TCP/IP protocol that's not a standard or Microsoft-based protocol.
The RSLinx installation on Computer B has only the features of it's license; if it's RSLinx Lite it just provides services to RSLogix and RSNetworx. RSLinx OEM/Pro/GW will provide OPC services to RSView or other OPC clients, and RSLinx Pro/GW will provide DDE services to Microsoft DDE clients.
The second mode is for RSLinx Gateway on Computer A to provide data services to client programs on Computer B using Remote OPC or NetDDE. RSLinx isn't involved on Computer B.
This is the mode you likely want to use, in which you set up "DDE Shares" and add the Computer A computer name to the DDE syntax in Excel on Computer B.
NetDDE is a pretty old technology, but it's what Excel uses. Search the RA Knowledgebase with the keywords "NetDDE Excel"
for a walk down operating system memory lane.