IP Address on Win XP Pro

[meese]

You may need to foreward the port that messenger uses. I will see if I can find that for you. As far as p2p, I haven't touched anything on my router (I have the same one you do) and they work.

Here is some info on messenger ports this comes from an article on how to disbale the messenger service:

Blocking Network Access to the Messenger Service
Blocking access to the service is complicated because it can communicate over multiple protocols, and it shares a port mapper with other applications. Blocking all the possible ports will disable the ability of other computers to send you messages, but it will also disable other services. The most common service that may be affected is Windows file sharing. If you want to share a folder on your computer to the network, this ability may be affected. If you don't want to share a folder across your network, blocking these ports is suggested as a way to improve overall security:

Block access to ports 135, 137-139, and 445. The default configuration of the Internet Connection Firewall shipped with Windows XP will block these ports. Windows NT, 2000, and XP TCP/IP security and filtering options in the network control panel can also be used to block ports. If you have a personal firewall (like BlackICE or ZoneAlarm) you can configure it to block inbound traffic on those ports.

Possible issues with blocking Messenger ports:
- Microsoft Outlook clients can talk to Microsoft Exchange servers on TCP 135
- Windows file sharing requires TCP 139 or 445 depending upon OS
- Server operators, managed networks, and people with custom applications should take great care with blocking ports. Domains and trusts require several of these ports for authentication and other things.
- Some third party applications, particularly management oriented ones may require TCP 135
- Windows Media Technology (also known as NetShow) uses TCP 135 for the Windows Media Administrator and Windows Media Encoder
- According to Microsoft, "Microsoft Office suite and other applications are DCOM aware. You may disable functionality that is in use by blocking ports."
- UDP 137 is needed for netbios name resolution. It and port 138 may be needed for access to netbios resources on the network.
- Some RPC based services exist on high ports (those greater than 1024). It may be possible that those services can be accessed and exploited directly bypassing the mapper on 135.

[Siliconjunkie]

Dispite what all those obnoxious pop ups say, there is no way to hide your IP address and have things still work. Think of it like sending a letter. If you send a letter to me and expect me to write back I have to have your address. TCP/IP is the same. Can't expect anyone to be able to reply to you if they dont know your address.

[NDuser]

Okay...that explains things a bit....thanx for the thelp and ino all!

[ragskash]

Hi Meese:

I am not able to make my outlook 2003 work with RPC over HTTP protocol.

I am using XP on my client side and SBS2003 server on the Server side connected to SMS wirelss router whith ports 80,110,25,1723, 443, 445 open. I followed the procedures for the RPC over HTTP and still I get error " Microsoft Exchange server unavailable".

Can u please help


I have Linksys router connected at my client side.

Thanks