cannot "remote access" between PC's on LAN through a switch

cannot "remote access" between PC's on LAN through a switch.

I have 2 PC's (WinXP Pro) on a LAN through a switch, each with it's own unique IP address.

- both PC's can access internet.
- I can file share/printer share between both PC's fine.

but I cannot use "remote desktop" OR "remote assistance "
the connection times out. also, don't no if this is related but I cannot play games over LAN.

you may assume no firewalls were enabled during tests.

I used to be able to do 'remote access' and games over LAN.

 

By accessing the internet do you mean only http protocol stuff or everything like ftp, ssh, telnet etc?

it does sound like some ports have been blocked, just check to make sure the windows xp built in firewall isn't on.

 

Yes, both PC's have FULL access to any protocol on the net, i use instant chat/ftp/http/and fileshareing on both PC's with no problem

WinXP firewall is disabled on both PC's as I use zonealarm (which was also disabled during tests)

 

There is a remote service bugfix available from microsoft in the windows xp updates from windowsupdate or try finding information on Q308210 article

Update:

This is the knowledge base article that may assist you:

support.microsoft.com/default.aspx?scid=kb;[LN];Q308210


Good luck!

 

thnx,

i got all updates though

 

also, i cannot transfer files over MSN messenger


note: i CAN do remote access with both PC's, just not with each other!! same with file transfer over msn messenger!!


is there something else that can be blocking ports????

 

Gasolene - let me make sure I got it right here.

- With either XP-pro system you can both send remote assistance messages and control/allow remote desktop control as long as the other PC is on the internet.

- Your local PCs will neither send an assistance request or allow remote control from the other one.

- Same with MSN Messenger. You can send files to internet locations but not to your other PC.

- This happens with no firewall running. Not hardware. Not software.

Do you get errors when you try? Are there any event log messages that seem related.

Because if the above items are accurate, this one is really strange.

 

Newt

Look back at former post http://windowsbbs.com/showthread.php?s=&threadid=12037&highlight=gasolene

It looks as though he is retrieving DHCP from the WAN that gets applied to the LAN. If so he is going outside and coming back in.

Possibly to tshoot this further he probably needs to disconnect the router. Then get his local lan setup and working properly before reconnecting.

That is all I can think of from here. Sure would like to be there to see and feel this one.

Mike

 

YES

YES

YES

YES, (no firewall hard/soft running)

the requesting machine sends requests for remote assistance
recieving machine gets confirmation dialog, then press OK to accept
then recieving machine gets 'no responce' after a while
requesting machine gets 'no responce' after a while

 

i resolved all my problems from prior post exept the 'remote assistance' so it may not hav been related (prob quoincidence)

i hav no router, only switch

local lan seems to work fine, filesharing and printsharing all working, machines communicate using IPX/SPX/NetBios

i seem to hav no trouble communicating with other machine using that protocol, it is when i try to communicate with other machine over internet that i hav problems

 

No Router?

So your Internet connection is a DSL or Cable modem connected to the switch?

Mike

 

yes adsl modem connected to switch

D-Link DSL-3001

 

Since you do not have a router, only a ADSL modem connected to a switch, are the public IP addresses used on the same subnet/network?

Uninstall ZoneAlarm rather than just disabling it.

 

no the IP's are on different subnet, but this should matter since they are communicating over internet right?
just as though i were communicating with any other machine on the net.

 

If your PCs are on different subnets, they have to be communicating thru a router. One at your ISP almost certainly.

And all I can think of for a cause is some setting on the router(s) between your two PCs. If you are interested, you can do a traceroute from one PC to the other and get a list of all the routers the packets pass thru to get from PCa to PCb at your house. But since you don't control the router(s), it will be tough to find out what setting(s) are giving you problems. Most tech support folk at the ISP won't be tech enough to know probably.

If this is something you really want or need to do, I see one good possiblilty at this point. Add a 2nd NIC to each PC. Set them to fixed addresses and use a private series. 192.168.x.x is easy or 10.x.x.x and use a netmask of 255.255.255.0 with either series. Then put a hosts file on each PC that contains only the two private addresses and associated name. Then run your remote calls thru those and you won't be dealing with any internet-based equipment at all.

 

I read this post quickly,

I would go with Newts last suggestion. Accept just use the same subnet masks. I don't see any reason for 2 more nics. Remote desktop, remote assistance and gaming all insinuate your leaving your local lan. I don't see any reason to go past your switch. With your switch you don't need to have different subnets.
You said you can connect them both, send outside, and receive.

Basically,

1--the router at your DSL company is receiving your request for information:
Thats in your computer "Same Connection "
to return to you. "Same Connection "
The router is probably reading the requests as errors from your Lan. Thinking your router is releasing packets by mistake. It's following protocol.
Your asking it to ask you for info to return to you.

Rookie
- -

But of course, i could be wrong. I never said i was an expert. Just seems correct at this time.

 

Rookie

Thats what I tried to say. Lol!

But you said it so much better! You crack me up!

Gasolene, you have an unusual setup to say the least.

I think the best thing to do is get a router. But before that disconnect the dsl. So that you can see the true LAN, where it fails etc. Get it corrected then reconnect the dsl thru the router.

As you say most things seem to work. But on the internet you can go around the world to get next door.

Mike