• Important! If you attempt to register and do not get an email within 5 minutes please check your spam box. This is especially true for Microsoft owned domains like Hotmail, Outlook, and Live. If these do not work please consider Gmail. Yahoo, or even AOL email which works fine.
  • JUOT.ORG NOW ACTIVE

    Please update any bookmarks from juot.net to juot.org and start using it.

    The juot.net URL will be going away March 1st, 2025.

Connecting network printer directly to Win7 PC

Ralph

VIP
This is a configuration that works flawlessly under WinXP. I have upgraded to a Win7 PC. I am connecting said Win7 PC to a network printer directly. No router. A x/o cable is used. Typical TCP/IP settings - 192.168.3.4 for the printer's IP, 192.168.3.3 for the PC. No DHCP. Subnet mask 255.255.255.0 in both cases. There is no default gateway.

When I tried to set this up on the Win7 machine, Win7 recognizes the network as unidentified, so it treats it as Public and locks it down tight. I cannot communicate with the printer. If I go into Network & Sharing Center, where normally you would be able to change the network type (i.e. Home/Work/Public), by clicking on the network name (it's hyperlinked), there is no hyperlink. It is disabled.

How does one do this? Is using a router my only option?
 

abqtj

I'm a damn delight!
Staff member
Administrator
VIP
Holy shit, a 48 ft cable for that price? NICE
 

Ralph

VIP
delete the network from Win7 and retry?
I tried disconnecting the x/o cable, disabling/re-enabling the NIC in device manager, and reconnecting the cable. Still no dice.

I did wind up changing local security policy to supposedly allow these things. But still no luck. I also made sure it wasn't set to treat all new networks as public. Still no luck.
 

Sean Mallory

Legend in my own mind
And burning electricity. Not much but some.

Just try this

first, disable the NIC in Device Manager.

1) Open the "Control Panel"

2) Select and open "Network and Sharing Center"

3)Click on the "Icon"(a house icon for me) under "View your active networks". This will open the "Set Network Properties" dialogue. Here you can rename a network connection or change the icon for that network connection.

4)Click on "Merge or Delete Network Locations" to see a list of stored network connections. You can merge or delete connections here as well as see if a network connection is in use and managed or unmanaged.

Delete the broken network and reenable the NIC.
 

Justin

Damn.
VIP
Just a hunch here, but try this config again with a much shorter network cable, like 10 feet or less.
 

Ralph

VIP
Just a hunch here, but try this config again with a much shorter network cable, like 10 feet or less.
Is there a reason that this config would work with the 50' cable under WinXP and not 7? Do you suspect difference in NICs?

I only ask because that is impractical. The printer we're talking about is 36" wide x 30" deep, 24" high, and weighs 150 lbs.
 

themonk

ex-monk.
VIP
Will poke around with that a bit later.

I don't HAVE to do this without a router, but it would just be an extraneous piece of hardware that serves no purpose other than to be a band-aid.

I did get the device working via that USB repeater cable. At this point, I may just leave it, depending on how much this bugs the shit out of me :rotflmao:
Why do you feel you need to connect it via network versus USB? Any loss of functionality?

I used to do basically what you want on a much shorter range when working on certain printers (only way to do some troubleshooting was via web interface). Did it under Windows 7 without any issue. :shrug:
 

Ralph

VIP
Why do you feel you need to connect it via network versus USB? Any loss of functionality?

I used to do basically what you want on a much shorter range when working on certain printers (only way to do some troubleshooting was via web interface). Did it under Windows 7 without any issue. :shrug:
It has been connected by network for years because the distance used to be closer to 100'. When I moved it into the new shop, that distance cut in half. Now it's reachable by USB.

At this point, with it working by USB, I don't see a need to use ethernet any more. Again, this depends on whether I get a bug up my ass and want to just make the f*cking thing work.

The whole thread is essentially moot. The problem still exists but it is not of consequence. I would still like to solve the issue though.
 
Top