Unable to Setup TCP/IP printer from a winxp sp3 machine

Hi all,

I am having problem trying to setup a a standard TCP/IP printer for 2 workstations. We are on a 2003 domain, the computers are on WinXP SP3, both are on the same subnet, including the printer i setup.  I setup the printer and set a reservation on DHCP, on the same subnet where i have both computers im trying to setup exclusively on this printer. I tried setting up via adding printer and creating a TCP/IP port and it doesn't work. Tried couple of tcp/ip troubleshooting and both computer does return proper DNS and DHCP names and ip's.

What's weird is im unable to ping the computer vice versa. And obviously unable to ping the Printer. Another thing is, I was able to setup this printer on my own machine but im on a different subnet, though my network is setup to talk to all other network so it doesnt suprise me much. I am able to ping the Printer from my machine.

I am able to ping the PC's in question from my machine, and the PC's can ping my Machine, but not each other and not the printer. Remember, The printer, and the 2 PC's are on the same subnet, so i am not sure what's wrong.

The 2 PC's are able to connect to internet fine, shared folder, other network shared printer which is on the Directory, except this Printer i am trying to setup for them. The printer, and 2 PC's are attached to the same switch, and the ports they are connected are 100% member of the VLAn they suppose to belong to. They all have the 192.168.24.XX IP and subnet mask 255.255.255.0 mask.

Any help would be greatly appreciated! Thank you so much!
gihrnmAsked:
Who is Participating?
 
gihrnmAuthor Commented:
Sorry guys i was able to figure it out. I'm able to assign an IP to the printer and can browse it Fine. What i did is just assign the printer to a subnet where everyone can speak to it, and from then on put the printer on the Directory and assign who can access it by access list, and that solve my issue.

Big thank you guys for all of your help and opinions!
0
 
beechy_Commented:
Have you checked firewall exceptions for the local subnet on the two problem machines (ICMP and file/printer sharing)?  You could rule out the firewall altogether by temorarily disabling it altogether on your problem machines and seeing if the problem persists.
0
 
JaoibhCommented:
if its the one machine that has the problem connecting double check you havent typo'd the subnet or the IP address.

Apart from that Beechy is correct it must be a firewall disable it under control panel - firewall.
then try it. let us know how you get on
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
gihrnmAuthor Commented:
The Firewalls are disabled on the 2 machines.

And Jaoibh, sorry i didn't quite understand your first sentence. The 2 PC's im trying to setup with the printer are unable to ping each other, and the printer, but can ping my machine which is on a different subnet. If that clarifies your first statement.

Thanks!

0
 
JaoibhCommented:
ok,

So all have the 192.168.24.XX IP and subnet mask 255.255.255.0 mask

I was asking you to double check your IP addresses
start - run - CMD - IPCONFIG /all
and make sure that there are no incorrect IP's as I have done before. its easy to setup incorrectly.

the other thing I'd check is the cables and switch you are plugged into make sure they're is connectivity
0
 
gihrnmAuthor Commented:
Jaoibh,

Yes they are all alright i've done that. The DHCP DNS WINS servers are what's supposed to be and they are all reachble from the machine.
The network cables should be fine mate, you see im able to login any domain account, get to the internet, folder shares, encrypted shares, print to printers on the Print server etc..

Basically, the 2 PC's are able to access network resources, it just cannot ping the Printer i've setup for them, and cannot ping each other. And the firewall is turned off.

Thanks
0
 
JaoibhCommented:
hey

ok this is my last idea that I can come up with.
I had the problem where i couldnt connect to a network printer and this was the issue
the default group policy had
Microsoft network Client: digitally sign communications (always) defined
Microsoft network Client: digitally sign communications (If Server Agrees) Defind

its a long shot but its the best I can do without seeing your network.

Digital-Sign.JPG
0
 
gihrnmAuthor Commented:
So to what setting should i set it, Enabled?
0
 
JaoibhCommented:
well check there and the default domain controllers policy and see if its enabled and if it is set it to "not defined"

If its not it I havent the foggiest I'll have to have a think about it
0
 
AngloCommented:
What swirtches do you have?  I seem to remember a setting some time ago where although it is a switch it can be set to channel all traffic to an uplink only (into your router).  I believe this was brought in by some manufacturers to handle video streaming before they got clever with the newer models.
0
 
gihrnmAuthor Commented:
Jaobih, its enabled. And on my PC its also enabled which works for the Printer im trying to setup. And also, this doesn't explain why the 2 pc's im setting up for the printer, is unable to ping each other. There some networking factor on this more likely.

Anglo, We have Allied Telesyn for our switches. Does this ring a bell?
Thanks
0
 
captainCommented:
Hi

real stupid question, does the printer get an IP? It is not clear from your posts.

If the printer has a config page, worth printing this. this sounds like BootIP/DHCP is not enabled on the printer.

If you get an IP and you know what it is see if you can http to the printer using the IP in your browser.

Just thinking out loud to cross the obvious off the list.
capt.
0
 
Dave BaldwinFixer of ProblemsCommented:
Ping (ICMP) can be disabled in Windows XP in the Windows Firewall 'Advanced' settings.
0
 
Davis McCarnOwnerCommented:
Allied Telesyn makes everything under the sun and, if it is a managed switch, might easilly be routing the traffic so it won't return to their subnet.  You might want to try the free version of pingplotter ( http://www.pingplotter.com/freeware.html ) to see the routing.
What happens if you try to open the printer's admin page from either system?  And, you might try sharing a folder on one of the systems just to see what happens then.  Lastly, what Antivirus and does it have a firewall component?
 
0
 
c661jmbCommented:
First of all if you are using different subnets what gateways have you got set? How do the PC's know how to get to the other subnet? Have you assigned a static route?

If you are having trouble even pinging the machines then I would suggest you look at routes and gateways.

IPCONFIG /ALL

Route /Print

let us know the results from both the PC's

0
 
AngloCommented:
Yes it was an allied switch I was thinking of.  What model is it?
0
 
Davis McCarnOwnerCommented:
So it was a routing problem!
0
 
AngloCommented:
Hi I remember this now you have prompted me.  Not sure about newer switches.

The Rapier series did this:
Private VLANs
A private VLAN contains switch ports that are isolated from other ports in the
VLAN, but can access another network through an uplink port or uplink trunk
group. These ports are called private ports. Private ports may be standalone or
be combined into groups. Standalone private ports can only communicate with
the uplink port, not with other ports in the VLAN. Private ports that are in a
group can communicate with other ports in the group and with the uplink
port, but cannot communicate with the other private ports in the VLAN.
The switch forwards traffic between private ports and the uplink port, and
between private ports within a group, according to its normal forwarding
rules. The only difference is that forwarding to other private ports is blocked
unless the ports are in the same group. Note that all traffic between private
ports is blocked, not only Layer 2 traffic.
A typical application is a hotel installation where each room has a port that can
access the Internet. In this situation it is undesirable to allow communication
between rooms. Another application is to simplify IP address assignment.
Ports can be isolated from each other while belonging to the same subnet.

taken from http://www.alliedtelesis.co.nz/documentation/rapier/273/pdf/swi-rp.pdf
0
 
gihrnmAuthor Commented:
Hi Anglo, is this also a good measure to prevent spread of Virus? Let's say, one machine has been infected, if it cannot speak to other machine as you said, then it will not spread the virus i would assume?
0
 
AngloCommented:
It would certainly isolate all machines so that a virus that is trying to spread by scanning for ip's on the subnet would get no responses.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.