I have a customer who shares a wireless router with the business below him (the location of said router). So I couldn't set up his 1820 to the "network". So I wired an ethernet connection from Copier to PC and gave his Local Area Connection a fixed IP address. But his internet is now not working because it wants to use the LAC instead of the Wireless. Is there a way to make the Wireless his primary network connection and still use the copier on the LAC?

Also I got nothing but errors on SMB scanning, does SMB not work with this kind of setup?

Thanks!

I have not seen this kind of issue since Windows 98.

However, I've been running Win 2000 and XP Professional editions ever since dumping Win98. Yes I do nearly the same thing with my PC in the office when testing machines, and it works fine. The wireless is on the office LAN, and the wired is directly connected by crossover cable to whatever I'm testing and static IP's.

Perhaps XP and Vista home editions don't work so nicely like this?

The SMB issue may be firewall and/or user permissions not set to read/write for the shared folder. Bottom line is that it can work.

Using two TCP/IP connections on the same PC requires using different IP schemes to prevent confusion for the pc:

For Example - the wireless router provides:
IP: 192.168.1.103
Subnet: 255.255.255.0
Gateway: 192.168.1.1

The wired ethernet IP should be something like:
IP: 192.168.2.1
Subnet 255.255.255.0
Gateway is blank
DNS is blank

Of course the MFP would be something like
IP: 192.168.2.2
Subnet 255.255.255.0

If you use the same family of numbers the PC gets confused as to which direction it should be looking and you can get some strange results. The gateway address is telling it where to go to look for stuff outside of the LAN (for example - the Internet) - so eliminating it completely from the wired interface will prevent it from looking it's direction.

That makes perfect sense, I didn't even think of that. Thanks bud, you too Chris (you probably gave me the benefit of knowing not to do that).